<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Fri, 02 Oct 2026 19:49:39 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-252280</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-252280</link>
      <description>EUVD-2026-252280</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-252280</guid>
    </item>
    <item>
      <title>fkie_cve-2025-57766</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-57766</link>
      <description>&lt;p&gt;Fides is an open-source privacy engineering platform. Prior to version 2.69.1, admin UI user password changes in Fides do not invalidate active user sessions, creating a vulnerability chaining opportunity where attackers who have obtained session tokens through other attack vectors (such as XSS) can maintain access even after password reset. This issue is not directly exploitable on its own and requires a prerequisite vulnerability to obtain valid session tokens in the first place. Version 2.69.1 fixes the issue. No known workarounds are available.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Fides is an open-source privacy engineering platform. Prior to version 2.69.1, admin UI user password changes in Fides do not invalidate active user sessions, creating a vulnerability chaining opportunity where attackers who have obtained session tokens through other attack vectors (such as XSS) can maintain access even after password reset. This issue is not directly exploitable on its own and requires a prerequisite vulnerability to obtain valid session tokens in the first place. Version 2.69.1 fixes the issue. No known workarounds are available.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-57766</guid>
    </item>
    <item>
      <title>GHSA-rpw8-82v9-3q87 — Fides' Admin UI User Password Change Does Not Invalidate Current Session</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-rpw8-82v9-3q87</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: ethyca-fides&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;Admin UI user password changes in Fides do not invalidate active user sessions, creating a vulnerability chaining opportunity where attackers who have obtained session tokens through other attack vectors (such as XSS) can maintain access even after password reset. This issue is not directly exploitable on its own and requires a prerequisite vulnerability to obtain valid session tokens in the first place.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;Fides uses encrypted authentication tokens with extended expiration periods. When a password is changed via password reset endpoints, the system updates the password hash in the database but does not invalidate existing client sessions or tokens. The authentication system validates tokens based on their cryptographic integrity and expiration time, not against the current password state.&lt;/p&gt;
&lt;p&gt;The frontend application stores authentication state in browser local storage, which persists across browser sessions until explicit logout or natural token expiration.&lt;/p&gt;
&lt;p&gt;This behavior alone does not constitute a directly exploitable vulnerability. The security issue only becomes exploitable when chained with other vulnerabilities or conditions that allow attackers to obtain valid session tokens, such as:&lt;/p&gt;
&lt;p&gt;- Cross-Site Scripting (XSS) attacks that can access browser storage where tokens are stored
- Session hijacking through network interception
- Malware on the user&amp;#39;s device that can read browser storage
- Physical device access where attackers can access browser s…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: ethyca-fides&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;Admin UI user password changes in Fides do not invalidate active user sessions, creating a vulnerability chaining opportunity where attackers who have obtained session tokens through other attack vectors (such as XSS) can maintain access even after password reset. This issue is not directly exploitable on its own and requires a prerequisite vulnerability to obtain valid session tokens in the first place.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;Fides uses encrypted authentication tokens with extended expiration periods. When a password is changed via password reset endpoints, the system updates the password hash in the database but does not invalidate existing client sessions or tokens. The authentication system validates tokens based on their cryptographic integrity and expiration time, not against the current password state.&lt;/p&gt;
&lt;p&gt;The frontend application stores authentication state in browser local storage, which persists across browser sessions until explicit logout or natural token expiration.&lt;/p&gt;
&lt;p&gt;This behavior alone does not constitute a directly exploitable vulnerability. The security issue only becomes exploitable when chained with other vulnerabilities or conditions that allow attackers to obtain valid session tokens, such as:&lt;/p&gt;
&lt;p&gt;- Cross-Site Scripting (XSS) attacks that can access browser storage where tokens are stored
- Session hijacking through network interception
- Malware on the user&amp;#39;s device that can read browser storage
- Physical device access where attackers can access browser s…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-rpw8-82v9-3q87</guid>
    </item>
    <item>
      <title>PYSEC-2026-1348 — Fides' Admin UI User Password Change Does Not Invalidate Current Session</title>
      <link>https://cve.radiocsirt.org/vuln/pysec-2026-1348</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: ethyca-fides&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;Admin UI user password changes in Fides do not invalidate active user sessions, creating a vulnerability chaining opportunity where attackers who have obtained session tokens through other attack vectors (such as XSS) can maintain access even after password reset. This issue is not directly exploitable on its own and requires a prerequisite vulnerability to obtain valid session tokens in the first place.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;Fides uses encrypted authentication tokens with extended expiration periods. When a password is changed via password reset endpoints, the system updates the password hash in the database but does not invalidate existing client sessions or tokens. The authentication system validates tokens based on their cryptographic integrity and expiration time, not against the current password state.&lt;/p&gt;
&lt;p&gt;The frontend application stores authentication state in browser local storage, which persists across browser sessions until explicit logout or natural token expiration.&lt;/p&gt;
&lt;p&gt;This behavior alone does not constitute a directly exploitable vulnerability. The security issue only becomes exploitable when chained with other vulnerabilities or conditions that allow attackers to obtain valid session tokens, such as:&lt;/p&gt;
&lt;p&gt;- Cross-Site Scripting (XSS) attacks that can access browser storage where tokens are stored
- Session hijacking through network interception
- Malware on the user&amp;#39;s device that can read browser storage
- Physical device access where attackers can access browser s…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: ethyca-fides&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;Admin UI user password changes in Fides do not invalidate active user sessions, creating a vulnerability chaining opportunity where attackers who have obtained session tokens through other attack vectors (such as XSS) can maintain access even after password reset. This issue is not directly exploitable on its own and requires a prerequisite vulnerability to obtain valid session tokens in the first place.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;Fides uses encrypted authentication tokens with extended expiration periods. When a password is changed via password reset endpoints, the system updates the password hash in the database but does not invalidate existing client sessions or tokens. The authentication system validates tokens based on their cryptographic integrity and expiration time, not against the current password state.&lt;/p&gt;
&lt;p&gt;The frontend application stores authentication state in browser local storage, which persists across browser sessions until explicit logout or natural token expiration.&lt;/p&gt;
&lt;p&gt;This behavior alone does not constitute a directly exploitable vulnerability. The security issue only becomes exploitable when chained with other vulnerabilities or conditions that allow attackers to obtain valid session tokens, such as:&lt;/p&gt;
&lt;p&gt;- Cross-Site Scripting (XSS) attacks that can access browser storage where tokens are stored
- Session hijacking through network interception
- Malware on the user&amp;#39;s device that can read browser storage
- Physical device access where attackers can access browser s…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/pysec-2026-1348</guid>
    </item>
  </channel>
</rss>
