CVE-2025-53942: Authentik has insufficient check for account active status when authenticating with OAuth/SAML Sources
(updated )
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.
References
- github.com/advisories/GHSA-9g4j-v8w5-7x42
- github.com/goauthentik/authentik
- github.com/goauthentik/authentik/commit/7a4c6b9b50f8b837133a7a1fd2cb9b7f18a145cd
- github.com/goauthentik/authentik/commit/c3629d12bfe3d32d3dc8f85c0ee1f087a55dde8f
- github.com/goauthentik/authentik/commit/ce3f9e3763c1778bf3a16b98c95d10f4091436ab
- github.com/goauthentik/authentik/security/advisories/GHSA-9g4j-v8w5-7x42
- nvd.nist.gov/vuln/detail/CVE-2025-53942
Code Behaviors & Features
Detect and mitigate CVE-2025-53942 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →