Skip to content
Fencer Vulns
medium 4.8

CVE-2025-64521 json

authentik deactivated service accounts can authenticate to OAuth

published 2025-11-19 11 mo ago modified 2026-10-18 21 d ago also BIT-authentik-2025-64521 , EUVD-2025-198186 , GHSA-xr73-jq5p-ch8r , GO-2025-4137 , PYSEC-2025-237

cvss
4.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 14%
public exploits
0
none known

Summary

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.

Patch / fix

  • go goauthentik.io 0.0.0-20251119140106-9dbdfc3f1be0
  • bitnami authentik 0.0.0-20251119140106-9dbdfc3f1be0, 2025.8.5, 2025.10.2
  • pypi authentik-client 2025.8.5, 2025.10.2
  • goauthentik authentik 0.0.0-20251119140106-9dbdfc3f1be0, 2025.8.5, 2025.10.2
  • govulncheck-vulndb openSUSE Leap 15.6 0.0.20251230T014957-150000.1.134.1

suse advisories SUSE-SU-2026:0037-1

  • govulncheck-vulndb openSUSE Leap 16.0 0.0.20260723T184607-160000.1.1

opensuse advisories openSUSE-SU-2026:21483-1

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
11 mo ago

Exploit prediction

0.23% chance of exploitation in the next 30 days, higher than 14% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 4.8 CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N
GitHub 3.1 4.8 CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N
OSV 3.1 4.8 CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N

Affected packages

ecosystem package affected fixed in
go goauthentik.io
<0.0.0-20251119140106-9dbdfc3f1be0
all versions
0.0.0-20251119140106-9dbdfc3f1be0
bitnami authentik
<0.0.0-20251119140106-9dbdfc3f1be0
>=2000.0.0, <2025.8.5
>=2025.9.0, <2025.10.2
0.0.0-20251119140106-9dbdfc3f1be0
2025.8.5
2025.10.2
pypi authentik-client
>=2025.8.0, <2025.8.5
>=2025.10.0, <2025.10.2
2025.8.5
2025.10.2

Affected products

  • goauthentik authentik

Classification

Weakness
  • CWE-289 Authentication Bypass by Alternate Name
  • CWE-286 Incorrect User Management

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.