CVE-2025-64521: medium-severity vulnerability in goauthentik authentik
authentik deactivated service accounts can authenticate to OAuth
Published
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
13Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 4.8epss 0.2%
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.
CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N
Affected products
goauthentik · authentikRelated CVEs — goauthentik authentik
In the same product, most dangerous first.
CVE-2022-46145HIGHauthentik vulnerable to unauthorized user creation and potential account takeoverEPSS 1.3%CVE-2023-48228HIGHOAuth2: PKCE can be fully circumventedEPSS 1.2%CVE-2024-52289HIGHauthentik has an insecure default configuration for OAuth2 Redirect URIsEPSS 1.1%CVE-2022-23555CRITICALauthentik vulnerable to Improper Authentication via invitation URL token reuseEPSS 0.9%CVE-2026-25227CRITICALauthentik affected by Remote Code Execution via Context Key Injection in PropertyMapping Test EndpointEPSS 0.9%CVE-2023-46249CRITICALauthentik potential installation takeover when default admin user is deletedEPSS 0.8%