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

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

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 12 Feb 2026
- **Updated:** 17 Feb 2026
- **Also known as:** BIT-authentik-2026-25922, GHSA-jh35-c4cc-wjm4

## 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 (Improper Verification of Cryptographic Signature), CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2026-25922?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `authentik` | Bitnami | All versions | 2025.8.6, 2025.12.4 |

Products: 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.

## Is CVE-2026-25922 being exploited?

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

## Other vulnerabilities in goauthentik authentik

- [CVE-2026-49448](https://insights.sbomify.com/CVE-2026-49448/): authentik: SourceStage bypass via empty POST (critical 9.8)
- [CVE-2023-46249](https://insights.sbomify.com/CVE-2023-46249/): authentik potential installation takeover when default admin user is deleted (critical 9.7)
- [CVE-2022-23555](https://insights.sbomify.com/CVE-2022-23555/): authentik vulnerable to Improper Authentication via invitation URL token reuse (critical 9.4)
- [CVE-2026-42849](https://insights.sbomify.com/CVE-2026-42849/): authentik: Reflected XSS in SFE AutosubmitStage allows IDP account takeover (critical 9.3)
- [CVE-2026-25227](https://insights.sbomify.com/CVE-2026-25227/): authentik affected by Remote Code Execution via Context Key Injection in PropertyMapping Test Endpoint (critical 9.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-25922 and fix it if it is affected.

What it is: 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.
Exploitation: There is no known exploitation of CVE-2026-25922 in the wild and no public exploit code.

Affected packages and fixed versions:
- authentik (Bitnami): affected all versions; fixed in 2025.8.6, 2025.12.4

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-25922/ (Markdown: https://insights.sbomify.com/CVE-2026-25922/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-25922
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-25922
- OSV: https://osv.dev/vulnerability/CVE-2026-25922

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-25922/
Summaries are generated and may contain mistakes; the official description above is the record.