CVE-2026-47201: authentik: XML Signature Wrapping in SAML Source ACS allows authentication as arbitrary federated user

Published May 29, 2026
·
Updated

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

Other sources

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.

MITRE

Affected Software

4 affected componentsFixes available
go/goauthentik.io<0.0.0-20260528144335-a370d76d23c7
0.0.0-20260528144335-a370d76d23c7
goauthentik Authentik<2025.12.6
goauthentik Authentik>=2026.2.0<2026.2.4
goauthentik Authentik>=2026.5.0<2026.5.1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade go/goauthentik.io to a version that resolves this vulnerability.

    Fixed in 0.0.0-20260528144335-a370d76d23c7
  2. Upgrade

    Upgrade authentik to a version that resolves this vulnerability.

    Fixed in 2025.12.5
  3. Upgrade

    Upgrade authentik to a version that resolves this vulnerability.

    Fixed in 2026.2.3
  4. Upgrade

    Upgrade authentik to a version that resolves this vulnerability.

    Fixed in 2026.5.1
  5. Compensating control

    Disable affected authentik SAML Sources used for upstream SAML federation with signed assertions / signed responses without signed assertions.

  6. Compensating control

    Block access to affected authentik SAML Source ACS endpoints.

Event History

May 29, 2026
Advisory Published
via GitHub·08:25 PM
Data Sourced
via GitHub·08:25 PM
DescriptionSeverityWeaknessAffected Software
Jun 2, 2026
CVE Published
via MITRE·08:30 PM
Data Sourced
via MITRE·08:30 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·09:16 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-47201?

The severity of CVE-2026-47201 is rated high with a score of 8.5.

2

What vulnerability does CVE-2026-47201 describe?

CVE-2026-47201 describes an XML Signature Wrapping vulnerability in authentik's SAML Source ACS endpoint, which can allow attackers to reuse valid signed assertions.

3

How do I fix CVE-2026-47201?

To fix CVE-2026-47201, upgrade to authentik version 2026.5.1 or 2026.2.4.

4

Who is affected by CVE-2026-47201?

Any user with an account at an upstream Identity Provider (IdP) can be affected by CVE-2026-47201.

5

What are the consequences of CVE-2026-47201?

The consequence of CVE-2026-47201 is that an attacker can authenticate as another federated user by exploiting reused valid signed assertions.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203