Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-57580 – Authentication Bypass / Account Takeover – authentik < 2026.2.6 and 2026.5.0–2026.5

Be the first to know when new zero-days emerge:

Summary

CVE-2026-57580 is a critical authentication bypass in authentik, an open-source Identity Provider, caused by an XML comment injection flaw (CWE-436, Interpretation Conflict) in inbound SAML source handling. The vulnerability enables full account takeover without the victim’s password or the identity provider’s private key, and carries a CVSS score of 9.4 (Critical).

Technical details

  • Root cause: authentik’s inbound SAML Source processing does not consistently handle XML comments embedded within the NameID field, so the value used for signature verification can differ from the value later used for user matching.
  • Trigger conditions: Exploitable only when a SAML Source is configured with a non-default user-matching mode — USERNAME_LINK or EMAIL_LINK. The default unique-identifier matching mode, and outbound SAML Provider functionality, are not affected.
  • Attack vector: An attacker who controls an account on the upstream (source) identity provider can set that account’s NameID to a value containing an injected XML comment. The comment causes the string used for account matching to be truncated in a way that matches a victim’s existing username or email, while the signed assertion remains cryptographically valid.
  • Impact: Binding of the attacker’s external identity to a victim’s existing authentik account, resulting in complete account takeover — no credentials or IdP signing key required.

Affected software

  • authentik versions prior to 2026.2.6
  • authentik versions 2026.5.0 up to (but not including) 2026.5.5

Severity

  • CVSS v4.0: 9.4 (Critical) — CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N
  • A CVSS v3.1 scoring of the same issue has also been published at 8.7 (High) — CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N

Mitigation and recommended actions

  • Immediate: Upgrade to authentik 2026.2.6 or 2026.5.5, whichever release line applies to your deployment.
  • If patching is not immediately possible:
    • Reconfigure any affected SAML Source to use the default unique-identifier matching mode instead of USERNAME_LINK or EMAIL_LINK (note this changes identity-linking behavior).
    • Add a SAML Source property mapping that rejects assertions containing XML comments in the NameID or attribute values.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge