CVE-2025-64521: authentik allows a deactivated Service account to authenticate to OAuth
Summary When authenticating with clientid and clientsecret to an OAuth provider, authentik creates a service account for the provider. In previous authentik versions, authentication for this account was possible even when the account was deactivated. Other permissions are correctly applied and federation with other providers still take assigned policies correctly into account.
Published Nov 19, 2025
Affected packages
goauthentik.io
- Ecosystem
- Go
- Affected
- < 0.0.0-20251119140106-9dbdfc3f1be0
- Fixed in
- 0.0.0-20251119140106-9dbdfc3f1be0
- Check
go list -m goauthentik.io
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
When authenticating with client_id and client_secret to an OAuth provider, authentik creates a service account for the provider. In previous authentik versions, authentication for this account was possible even when the account was deactivated. Other permissions are correctly applied and federation with other providers still take assigned policies correctly into account.
Patches
authentik 2025.8.5 and 2025.10.2 fix this issue, for other versions the workaround below can be used.
Workarounds
You can add a policy to your application that explicitly checks if the service account is still valid, and deny access if not.
return request.user.is_activeFor more information
If you have any questions or comments about this advisory:
- Email us at [[email protected]](mailto:[email protected]).
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 entriesCVE-2026-47201
authentik's XML Signature Wrapping in SAML Source ACS allows authentication as arbitrary federated user
high8.5May 29, 2026CVE-2025-64708
authentik's invitation expiry is delayed by at least 5 minutes
medium5.8Nov 19, 2025CVE-2025-53942
Authentik has insufficient check for account active status when authenticating with OAuth/SAML Sources
high7.1Jul 22, 2025CVE-2024-42490
GoAuthentik vulnerable to Insufficient Authorization for several API endpoints
critical8.7Aug 22, 2024CVE-2024-23647
Authentik vulnerable to PKCE downgrade attack
high6.5Jan 29, 2024
