What’s Vulnerable › Vulnerabilities
CVE-2025-64521: authentik deactivated service accounts can authenticate to OAuth
- Severity: medium (CVSS 4.8 v3.1)
- Exploited in the wild: not listed in CISA KEV
- EPSS: 0.2% probability of exploitation in the next 30 days
- Public exploit or detection template: none known
- Published: 2025-11-19 · updated 2026-10-18
- Weakness: CWE-289
Description
authentik is an open-source Identity Provider. Prior to versions 2025.8.5 and 2025.10.2, 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. authentik versions 2025.8.5 and 2025.10.2 fix this issue. A workaround involves adding a policy to the application that explicitly checks if the service account is still valid, and deny access if not.
Affected products
- goauthentik authentik: from 2025.8.0 before 2025.8.5; from 2025.10.0 before 2025.10.2 — fixed in 2025.10.2, 2025.8.5
How to fix
Upgrade to a fixed version: goauthentik authentik 2025.10.2, 2025.8.5. Check the vendor advisory for mitigations.
References
- https://github.com/goauthentik/authentik/commit/9dbdfc3f1be0f1be36f8efce2442897b2a54a71c
- https://github.com/goauthentik/authentik/security/advisories/GHSA-xr73-jq5p-ch8r
Get alerted when CVE-2025-64521 or the next vulnerability affects your stack