CVE-2025-53942: authentik has an insufficient check for account active status during OAuth/SAML authentication
Summary
Deactivated users that had either enrolled via OAuth/SAML or had their account connected to an OAuth/SAML account can still partially access authentik even if their account is deactivated. They end up in a half-authenticated state where they cannot access the API but crucially they can authorize applications if they know the URL of the application.
Patches
authentik 2025.4.4 and 2025.6.4 fix this issue.
Workarounds
Adding an expression policy to the user login stage on the respective authentication flow with the expression of
py return request.context["pendinguser"].isactive
This expression will only activate the user login stage when the user is active.
For more information
If you have any questions or comments about this advisory:
- Email us at security@goauthentik.io.
Other sources
authentik is an open-source Identity Provider that emphasizes flexibility and versatility, with support for a wide set of protocols. In versions 2025.4.4 and earlier, as well as versions 2025.6.0-rc1 through 2025.6.3, deactivated users who registered through OAuth/SAML or linked their accounts to OAuth/SAML providers can still retain partial access to the system despite their accounts being deactivated. They end up in a half-authenticated state where they cannot access the API but crucially they can authorize applications if they know the URL of the application. To workaround this issue, developers can add an expression policy to the user login stage on the respective authentication flow with the expression of return request.context["pendinguser"].isactive. This modification ensures that the return statement only activates the user login stage when the user is active. This issue is fixed in versions authentik 2025.4.4 and 2025.6.4.
— MITRE
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2025-53942?
The severity of CVE-2025-53942 is considered high due to the risk of deactivated users retaining partial access to the system.
How do I fix CVE-2025-53942?
To fix CVE-2025-53942, update your version of the goauthentik package to a version higher than 0.0.0-20250722122105-7a4c6b9b50f8.
What are the implications of CVE-2025-53942?
CVE-2025-53942 allows deactivated users to remain in a half-authenticated state, potentially leading to unauthorized information exposure.
Which software versions are affected by CVE-2025-53942?
CVE-2025-53942 affects goauthentik.io version 0.0.0-20250722122105-7a4c6b9b50f8 and earlier.
Who is impacted by CVE-2025-53942?
Users who enrolled via OAuth/SAML and have their accounts deactivated may be adversely affected by CVE-2025-53942.