CVE-2026-40165: authentik: SAML NameID XML Comment Injection Enables Authentication Bypass via Identifier Truncation
authentik is an open-source identity provider. Versions 2025.12.4 and prior, and versions 2026.2.0-rc1 through 2026.2.2 were vulnerable to Authentication Bypass through SAML NameID XML Comment Injection. Due to how authentik extracted the NameID value from a SAML assertion, it was possible for an attacker to trick authentik into only seeing a part of the NameID value, potentially allowing an attacker to gain access to other accounts. This issue could be exploited on an authentik instance with a SAML Source, where the attacker had an account on the SAML Source and the ability to modify their NameID value (commonly username or E-mail), and XML Signing was enabled. The attacker could modify the SAML assertion given to authentik by injecting a comment within the NameID value, which effectively truncated the NameID value to the snippet before the comment, and gave the attacker access to any user account. This issue has been fixed in versions 2025.12.5 and 2026.2.3.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
authentikto a version that resolves this vulnerability.Fixed in 2025.12.5 - Upgrade
Upgrade
authentikto a version that resolves this vulnerability.Fixed in 2026.2.3
Event History
Frequently Asked Questions
What is the severity of CVE-2026-40165?
The severity of CVE-2026-40165 is classified as high due to its ability to allow authentication bypass.
How do I fix CVE-2026-40165?
To fix CVE-2026-40165, upgrade authentik to version 2025.12.5 or later, or to versions beyond 2026.2.2.
What software is affected by CVE-2026-40165?
CVE-2026-40165 affects authentik versions 2025.12.4 and prior, as well as versions 2026.2.0-rc1 through 2026.2.2.
What is the nature of the vulnerability in CVE-2026-40165?
CVE-2026-40165 involves SAML NameID XML Comment Injection, which enables authentication bypass via identifier truncation.
Are there any workarounds for CVE-2026-40165?
There are no known effective workarounds for CVE-2026-40165; the recommended action is to upgrade to a fixed version.