NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · Go

CVE-2025-53942: Authentik has insufficient check for account active status when authenticating with OAuth/SAML Sources

highCVSS 4.0 7.1GHSA-9g4j-v8w5-7x42

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.

Published Jul 22, 2025 · Updated Jul 23, 2025

Affected packages

goauthentik.io

Ecosystem
Go
Affected
< 0.0.0-20250722122105-7a4c6b9b50f8
Fixed in
0.0.0-20250722122105-7a4c6b9b50f8
Check
go list -m goauthentik.io

Advisory details

From the GitHub Advisory Database (CC BY 4.0).

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:

Credited to pascalwei.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology

More Go vulnerabilities

All Go entries