GitHub Advisoryadvisory · Go

GHSA-9g4j-v8w5-7x42 Authentik has insufficient check for account active status when authenticating with OAuth/SAML Sources

HIGH Published 2025-07-22 Modified 2025-07-23 Official page ↗
Aliases
CVE-2025-53942
Ecosystem
Go
Packages
goauthentik.io
Severity
High
CVSS vector
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:H
Weaknesses
CWE-269
Reviewed
2025-07-22

Affected packages

• Go goauthentik.io: < 0.0.0-20250722122105-7a4c6b9b50f8 → fixed in 0.0.0-20250722122105-7a4c6b9b50f8

Description

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

Related

Alias · CVE (1)

  • CVE-2025-53942 authentik is an open-source Identity Provider that emphasizes flexibility and versatility, with support for a wide set of protocols. vulnerability

Weakness · CWE (1)

  • CWE-269 Improper Privilege Management weakness

References