Vulnerability · Published Nov 19, 2025 · Assigned by GitHub_M

CVE-2025-64521authentik deactivated service accounts can authenticate to OAuth

Medium 4.8

In plain English

A medium-severity security flaw in authentik from goauthentik. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 14% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS 3.1)4.8Medium
Exploit odds (30 days)0.2%top 85.6% of all CVEs
Exploited in the wildNo reportsCISA SSVC: none
Attack toolingNoneno public tooling known

Official 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 packages & fixed versions

EcosystemPackageFixed inAdvisory
Gogoauthentik.io0.0.0-20251119140106-9dbdfc3f1be0GHSA-xr73-jq5p-ch8r
Gogoauthentik.iono fix listedGO-2025-4137
PyPIauthentik-client2025.10.2, 2025.8.5PYSEC-2025-237

Affected products (as reported)

VendorProductVersions
goauthentik authentik < 2025.10.2< 2025.8.5

Weakness: CWE-289 · Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N

References