~ / search / GHSA-9g4j-v8w5-7x42

GHSA-9g4j-v8w5-7x42

Authentik has insufficient check for account active status when authenticating with OAuth/SAML Sources

Source: GitHub Advisory Database (reviewed) High CVE-2025-53942

Packages

EcosystemPackageAffectedFixed in
Go goauthentik.io < 0.0.0-20250722122105-7a4c6b9b50f8 0.0.0-20250722122105-7a4c6b9b50f8

Details

As written in the advisory (Markdown source, shown as plain text).

### 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]](mailto:[email protected]).

References

External links from the advisory. They lead to third-party sites.