CVE-2025-29928
HIGHDescription
authentik is an open-source identity provider. Prior to versions 2024.12.4 and 2025.2.3, when authentik was configured to use the database for session storage (which is a non-default setting), deleting sessions via the Web Interface or the API would not revoke the session and the session holder would continue to have access to authentik. authentik 2025.2.3 and 2024.12.4 fix this issue. Switching to the cache-based session storage until the authentik instance can be upgraded is recommended. This will however also delete all existing sessions and users will have to re-authenticate.
Is your site exposed to CVE-2025-29928?
Run a free security scan — no signup, results in seconds.
CVSS v3.1 Score
Weakness Type (CWE)
Affected Products
| Vendor | Product |
|---|---|
| goauthentik | authentik |
| goauthentik | authentik |
References
Frequently Asked Questions
What is CVE-2025-29928? +
How severe is CVE-2025-29928? +
What products are affected by CVE-2025-29928? +
How do I check if I'm vulnerable to CVE-2025-29928? +
Related Vulnerabilities
Affected versions of Flowintel do not revoke existing authenticated sessions when a user’s password is changed. This means that if …
An improper session validation allows an unauthenticated attacker to cause certain request notifications to be executed in the context of …
KTM System e-BOK allows the session identifier to be set by the client prior to authentication. If a cookie with …
tirreno, a security framework, has a session fixation issue in versions prior to 0.10.0. During authentication, tirreno validates the user's …
Session fixation vulnerability in Wikimedia Foundation OAuth. This vulnerability is associated with program files src/Backend/MWOAuthServer.Php. This issue affects OAuth: from …
A malicious actor can fix the session of a PAM user by tricking the user to click on a specially …