CVE-2026-47201: authentik's XML Signature Wrapping in SAML Source ACS allows authentication as arbitrary federated user
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.
Published May 29, 2026 · Updated Jun 9, 2026
Affected packages
goauthentik.io
- Ecosystem
- Go
- Affected
- < 0.0.0-20260528144335-a370d76d23c7
- Fixed in
- 0.0.0-20260528144335-a370d76d23c7
- Check
go list -m goauthentik.io
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
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 [[email protected]](mailto:[email protected])
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2025-64521
authentik allows a deactivated Service account to authenticate to OAuth
medium4.8Nov 19, 2025CVE-2025-64708
authentik's invitation expiry is delayed by at least 5 minutes
medium5.8Nov 19, 2025CVE-2025-53942
Authentik has insufficient check for account active status when authenticating with OAuth/SAML Sources
high7.1Jul 22, 2025CVE-2024-42490
GoAuthentik vulnerable to Insufficient Authorization for several API endpoints
critical8.7Aug 22, 2024CVE-2024-23647
Authentik vulnerable to PKCE downgrade attack
high6.5Jan 29, 2024
