CVE-2025-53942: authentik has an insufficient check for account active status during OAuth/SAML authentication

Severity: high (CVSS 7.4 v3.1)
Exploited in the wild: not listed in CISA KEV
EPSS: 0.6% probability of exploitation in the next 30 days
Public exploit or detection template: none known
Published: 2025-07-23 · updated 2026-06-17
Weakness: CWE-269

Description

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["pending_user"].is_active. 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.

Affected products

goauthentik authentik: before 2025.4.4; from 2025.6.0 before 2025.6.4 — fixed in 2025.4.4, 2025.6.4

How to fix

Upgrade to a fixed version: goauthentik authentik 2025.4.4, 2025.6.4. Check the vendor advisory for mitigations.

References

Get alerted when CVE-2025-53942 or the next vulnerability affects your stack