Loading...
Skip to main content

CVE-2026-47201 — authentik's XML Signature Wrapping in...

HIGH

authentik's XML Signature Wrapping in SAML Source ACS allows authentication as arbitrary federated user

Published May 29, 2026Updated June 9, 2026Source: osv

Summary

### Summary 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. ### Patches authentik 2026.5.1, 2026.2.4 and 2025.12.6 fix this issue. ### Impact Affected: authentik deployments using a SAML Source for upstream SAML federation with signed assertions, or signed responses without signed assertions. Not affected: deployments that do not use SAML Source for upstream SAML federation. The SAML Source trusts that the verified XML signature belongs to the assertion or response that authentik later consumes. A crafted SAML response can make signature verification succeed against the attacker's original signed assertion while authentik reads identity data from a different forged assertion. An attacker first completes a legitimate login to the upstream IdP and captures the signed SAML response sent through their browser. They then submit a modified response to the ACS endpoint where the valid signature still verifies, but the consumed assertion contains a victim identifier or attacker-chosen attributes. The attacker can authenticate as a victim who has previously used the SAML Source, or as a local user matched by forged email or username when those matching modes are enabled. ### Workarounds Disable affected SAML Sources, or block access to their ACS endpoints. ### For more information If there are any questions or comments about this advisory: - Send an email to [security@goauthentik.io](mailto:security@goauthentik.io)

Advisory Timeline

  • First published May 29, 2026 (136 days ago).
  • Last revised June 9, 2026 — 11 days after initial publication.

Remediation

Upgrade to the fixed version using your package manager.

Go
Update goauthentik.io to 0.0.0-20260528144335-a370d76d23c7 or later
go get goauthentik.io@v0.0.0-20260528144335-a370d76d23c7

After upgrading, run your dependency scanner again to confirm the vulnerability is resolved.

Affected Packages (1)

Affects 1 ecosystem: go (1).

PackageEcosystemAffectedFixed In
goauthentik.io
go
All versions0.0.0-20260528144335-a370d76d23c7

Vulnerability Classification

Common Weakness Enumeration (CWE) identifiers for this vulnerability type.

  • CWE-20
    Improper Input ValidationMITRE
  • CWE-287
    Improper AuthenticationMITRE
  • CWE-347
    Improper Verification of Cryptographic SignatureMITRE

CVSS Score Breakdown

What the CVSS (Common Vulnerability Scoring System) 8.5 score means for each attack dimension.

Attack Vector
Network
Attack Complexity
High
Privileges Required
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

Frequently Asked Questions

What is CVE-2026-47201?
authentik's XML Signature Wrapping in SAML Source ACS allows authentication as arbitrary federated user This vulnerability has been assigned a severity rating of HIGH (CVSS score: 8.5/10).
How do I check if my project is affected by CVE-2026-47201?
CVE-2026-47201 affects goauthentik.io. Use GeekWala's free vulnerability scanner to check your dependencies against CVE-2026-47201 and 200,000+ other known vulnerabilities.

Severity & Exploitability

CVSS Score
8.5

High exploitability or significant impact. Prioritize remediation within days.

Also Known As

GHSA-c3m2-jqmq-pvp3
BIT-authentik-2026-47201

Related CVEs

  • CVE-2024-42490
    CRITICAL

    GoAuthentik vulnerable to Insufficient Authorization for several API endpoints

  • CVE-2026-107809
    HIGH

    Nginx-UI AuthRequired token cookie fallback enables CSRF against management APIs

  • CVE-2025-53942
    HIGH

    Authentik has insufficient check for account active status when authenticating with OAuth/SAML Sources

  • CVE-2026-107813
    HIGH

    Nginx UI: Incomplete fix of CVE-2026-84315 - the api/cluster router was not - wrapped in RequireSecureSession, so those sensitive mutations run without OTP step-up

Check if you're affected

Scan your dependencies to see if this vulnerability affects your projects.

Scan Your Dependencies