CVE-2026-57580: goauthentik authentik · Interpretation Conflict
Affects goauthentik authentikSource CVE Database V5
Not known to be exploited · CVSS 9.4 Critical : upgrade to 2026.5.5 or 2026.2.6 as a priority.
Data as of 16 Nov 2026, 20:25 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 4.0 | 9.4 |
|---|
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 48% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2026.5.5, 2026.2.6
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 18 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.
What to do
Upgrade authentik and goauthentik/authentik to 2026.5.5 or 2026.2.6.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| goauthentikauthentik | Affected
| Fixed in
|
| goauthentikauthentik | Affected
| Fixed in
|
GitHubgoauthentik/authentikpkg:github/goauthentik/authentikOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade authentik to version 2026.2.6 or later, or 2026.5.5 or later, where this vulnerability is fixed. No other mitigation is indicated or required according to the vendor advisory.
Description
A critical vulnerability in goauthentik authentik prior to versions 2026.2.6 and 2026.5.5 allows an attacker with an account on the source identity provider to perform account takeover. The flaw involves an XML comment injection in the NameID field when using non-default user-matching modes (USERNAME_LINK or EMAIL_LINK), causing truncation of the interpreted value and enabling binding of the attacker's identity to a victim's account without needing the victim's password or the identity provider's private key. This issue does not affect the default unique-identifier matching mode or authentik's outbound SAML Provider role. The vulnerability is fixed in versions 2026.2.6 and 2026.5.5.
References
- github.com/goauthentik/authentik/security/advisories/GHSA-35v6-hv2g-6992 (opens in a new tab)
- github.com/goauthentik/authentik/pull/24057 (opens in a new tab)
- github.com/goauthentik/authentik/pull/24062 (opens in a new tab)
- github.com/goauthentik/authentik/commit/6bd00f09f1f6b5bc5212a10340418fa1b264f02c (opens in a new tab)
- github.com/goauthentik/authentik/commit/8704a1b89d7bf46bcef0d3c434c821b937fdecc3 (opens in a new tab)
- github.com/goauthentik/authentik/releases/tag/version/2026.2.6 (opens in a new tab)
- github.com/goauthentik/authentik/releases/tag/version/2026.5.5 (opens in a new tab)