Advisory

GHSA-9g4j-v8w5-7x42

Also known as: BIT-authentik-2025-53942, CVE-2025-53942, GO-2025-3822

Summary

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

Details

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

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:

Severity

High Basis: The source's own band: HIGH

Dates

Published
2025-07-22 14:31 UTC
Modified
2026-04-17 04:57 UTC

Affected packages and fixes

goauthentik.io

Go · All systems

Affected

  • introduced 0, fixed 0.0.0-20250722122105-7a4c6b9b50f8 (semver)

Fixed versions

0.0.0-20250722122105-7a4c6b9b50f8

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences