CVE-2025-29928: authentik's deletion of sessions did not revoke sessions when using database session storage
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.
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2025-29928?
CVE-2025-29928 is considered a medium-severity vulnerability due to its potential impact on session management.
How do I fix CVE-2025-29928?
To fix CVE-2025-29928, upgrade to authentik versions 2024.12.4 or 2025.2.3 or later.
What impact does CVE-2025-29928 have on session management?
CVE-2025-29928 can lead to sessions not being revoked properly when deleted via the Web Interface or API.
In which versions of authentik is CVE-2025-29928 present?
CVE-2025-29928 is present in authentik versions prior to 2024.12.4 and 2025.2.3.
What configuration is affected by CVE-2025-29928?
CVE-2025-29928 affects authentik configurations that use the database for session storage.