CVE-2026-25922 authentik has a Signature Verification Bypass via SAML Assertion Wrapping

High 8.8 Published Updated

Attackers can bypass SAML signature verification to inject malicious assertions, potentially taking over accounts in authentik identity provider deployments.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

What is CVE-2026-25922?

CVE-2026-25922 is a high-severity authentication bypass vulnerability in goauthentik authentik, published on 12 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.

Official description

authentik is an open-source identity provider. Prior to 2025.8.6, 2025.10.4, and 2025.12.4, when using a SAML Source that has the option Verify Assertion Signature under Verification Certificate enabled and not Verify Response Signature, or does not have the Encryption Certificate setting under Advanced Protocol settings configured, it was possible for an attacker to inject a malicious assertion before the signed assertion that authentik would use instead. authentik 2025.8.6, 2025.10.4, and 2025.12.4 fix this issue.

Weakness: CWE-347, CWE-287

Which versions are affected by CVE-2026-25922?

1 open source package ship an affected version, including authentik. It affects 1 product.

PackageAffectedFixed in
authentik BitnamiAll versions2025.8.6, 2025.12.4

Products include Goauthentik Authentik.

How do I fix CVE-2026-25922?

Upgrade authentik to a fixed version for your release line: 2025.8.6 or 2025.12.4.

Upgrade, and rotate credentials and sessions that may have been exposed. More about Authentication bypass.

Is CVE-2026-25922 being exploited?

There is no known exploitation of CVE-2026-25922 in the wild and no public exploit code.

Sources

Also known as BIT-authentik-2026-25922, GHSA-jh35-c4cc-wjm4.

Is CVE-2026-25922 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free