CVE-2025-57766Medium· 4.8▾ SunlitFides' Admin UI User Password Change Does Not Invalidate Current Session
▾ Sunlit zone — Low / medium · no exploitation signal
impact 26.4 · likelihood 0.1 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Exploit-prediction probability, daily snapshots since Jul 8.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via OSV
0.3%
0.3% → 0.3%
Last analysed / modified upstream
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.
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.
The frontend application stores authentication state in browser local storage, which persists across browser sessions until explicit logout or natural token expiration.
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:
This vulnerability serves as a persistence mechanism in attack chains rather than a primary attack vector. When chained with token theft vulnerabilities, it allows attackers to:
Stored tokens persist across browser sessions until explicit logout or natural expiration.
The vulnerability has been patched in Fides version 2.69.1. Users are advised to upgrade to this version or later to secure their systems against this threat.
There are no workarounds.
This vulnerability has been assigned a severity of LOW because:
This is fundamentally a defense-in-depth issue rather than a primary security vulnerability.
ethyca-fides < 2.69.1Upgrade to a patched release:
ethyca-fides 2.69.1Connected by shared product, vendor, weakness, or advisory.
CVE-2025-57817High· 7.2Fides Webserver API is Vulnerable to OAuth Client Privilege Escalation
CVE-2025-57816High· 7.5Fides Webserver API Rate Limiting Vulnerability in Proxied Environments
CVE-2025-57815Medium· 6.5Fides has a Lack of Brute-Force Protections on Authentication Endpoints
CVE-2023-36827High· 7.5ethyca-fides Webserver API Path Traversal vulnerability
CVE-2026-42303MediumEthyca Fides has a Privacy Request Identity Verification Bypass Vulnerability via Duplicate Detection
CVE-2026-44541Highethyca-fides has a DOM-based XSS vulnerability in fides.js via fides_description override