dbcve.org
AuthentikApplication · Goauthentik

CVE-2026-47201

HIGH · 8.5 CVSS v3.1 Published 2026-06-02
Fix available
A fix is available. Upgrade to 2025.12.6 / 2026.2.4 or later.
See remediation →
91/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
authentik is an open-source identity provider. Prior to versions 2025.12.5, 2026.2.3, and 2026.5.1, authentik's SAML Source ACS endpoint is vulnerable to XML Signature Wrapping when validating upstream SAML responses. An attacker with any account at the upstream IdP can reuse a valid signed assertion to authenticate as another federated user. This issue has been patched in versions 2025.12.5, 2026.2.3, and 2026.5.1.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

authentik's SAML Source ACS endpoint fails to properly validate XML signatures in upstream SAML responses, allowing XML Signature Wrapping (XSW) attacks. An attacker with any valid account at the upstream IdP can inject malicious XML elements into a signed SAML response while preserving the valid signature, enabling authentication as any federated user.

MitigationUpgrade authentik to version 2025.12.5, 2026.2.3, or 2026.5.1 which contain the patch for proper XML signature validation in the SAML ACS endpoint.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
AuthentikApplication
Affected:< 2025.12.6>= 2026.2.0, < 2026.2.4>= 2026.5.0, < 2026.5.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed authentik version
    Run 'authentik --version' or check the version through the admin UI under 'About' or in the container/container metadata
    Affected if Version is < 2025.12.6, or >= 2026.2.0 and < 2026.2.4, or >= 2026.5.0 and < 2026.5.1
  2. Identify SAML Source providers
    Navigate to the admin UI, go to 'Applications' or 'Providers' and list all providers of type 'SAML'
    Affected if Any SAML Source provider exists in the environment
  3. Verify SAML authentication is in use
    Check if any users authenticate via SAML by reviewing the 'Source' configuration in the admin UI under 'Authentication' -> 'Sources'
    Affected if SAML sources are configured and active for user authentication

If the installed authentik version falls within the affected ranges and SAML Source providers are configured and actively used for authentication, the environment is vulnerable to XML Signature Wrapping attacks allowing user impersonation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2025.12.6 / 2026.2.4 / 2026.5.1 or later
Fixed in 2025.12.62026.2.42026.5.1
Interim mitigation

Upgrade authentik to version 2025.12.5, 2026.2.3, or 2026.5.1 which contain the patch for proper XML signature validation in the SAML ACS endpoint.

Recommended fix High confidence

Upgrade to the latest version in your current branch: 2025.12.5 (for 2025.x), 2026.2.3 (for 2026.2.x), or 2026.5.1 (for 2026.5.x)

  1. 1. Identify the currently running Authentik version by checking the version endpoint or deployment configuration
  2. 2. Determine which version branch you are on (2025.x, 2026.2.x, or 2026.5.x)
  3. 3. For 2025.x branch: upgrade to version 2025.12.5 or later
  4. 4. For 2026.2.x branch: upgrade to version 2026.2.3 or later
  5. 5. For 2026.5.x branch: upgrade to version 2026.5.1 or later
  6. 6. After upgrading, verify the SAML Source authentication still works correctly
  7. 7. Test that the XML Signature Wrapping vulnerability is no longer exploitable by attempting to reuse a signed assertion from a different user
Caveat Standard upgrade precautions apply - review release notes for any configuration changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Authentik Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-47201 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-47201 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data