cve.bz

CVE-2025-64521 goauthentik authentik: Authentication Bypass by Alternate Name

4.8 mediumEPSS 0.2%Fix available

Medium (4.8) in goauthentik authentik. EPSS 0.2% estimated probability of exploitation activity in the next 30 days. Fixed in goauthentik.io 0.0.0-20251119140106-9dbdfc3f1be0.

On this page
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.

Severity

CVSS 3.1

4.8 medium
CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 14th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2025-11-19. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-289 Authentication Bypass by Alternate Name
OWASP Top 10
A07:2025 Authentication Failures
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2025-64521 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-64521?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-64521?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-64521 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
goauthentik:authentikfrom 2025.8.0 before 2025.8.5
goauthentik:authentikfrom 2025.10.0 before 2025.10.2

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-xr73-jq5p-ch8rGogoauthentik.io<0.0.0-20251119140106-9dbdfc3f1be00.0.0-20251119140106-9dbdfc3f1be0
GO-2025-4137Gogoauthentik.ioall versionsno fix published
PYSEC-2025-237PyPIauthentik-client>=2025.8.0 <2025.8.5
>=2025.10.0 <2025.10.2
2025.8.5, 2025.10.2

Linux distributions

DistributionReleasePackageFixed inAdvisory
openSUSELeap 15.6govulncheck-vulndb0.0.20251230T014957-150000.1.134.1SUSE-SU-2026:0037-1
openSUSELeap 16.0govulncheck-vulndb0.0.20260723T184607-160000.1.1openSUSE-SU-2026:21483-1

From the distributions' data via OSV.dev: SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: openSUSE.

References

Check your stackJSON