dbcve.org
AuthentikApplication · Goauthentik

CVE-2026-25922

HIGH · 8.8 CVSS v3.1 Published 2026-02-12
Fix available
A fix is available. Upgrade to 2025.8.6 / 2025.10.4 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

SAML assertion injection vulnerability in authentik where, when Verify Assertion Signature is enabled but Verify Response Signature is disabled, or when Encryption Certificate is not configured under Advanced Protocol settings, an attacker can inject a malicious assertion before the signed assertion that authentik will use for authentication, allowing unauthorized access.

MitigationUpgrade to authentik 2025.8.6, 2025.10.4, or 2025.12.4. Alternatively, ensure Verify Response Signature is enabled and Encryption Certificate is properly configured as temporary workarounds.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
AuthentikApplication
Affected:< 2025.8.6>= 2025.10.0, < 2025.10.4>= 2025.12.0, < 2025.12.4

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check authentik version
    Access the authentik admin UI, navigate to the about page or check the Docker container/image tag to determine the installed version number.
    Affected if The installed version falls into any of these ranges: < 2025.8.6, >= 2025.10.0 but < 2025.10.4, >= 2025.12.0 but < 2025.12.4
  2. Identify SAML Provider configurations
    In authentik admin UI, go to Providers and list all SAML Provider instances. Note each provider name and the associated application.
    Affected if Any SAML Provider exists in the environment - the vulnerability applies to providers, not the overall installation.
  3. Verify Response Signature setting
    For each SAML Provider, open the provider settings and locate the Signature Verification section. Check whether 'Verify Response Signature' is enabled or disabled.
    Affected if 'Verify Response Signature' is disabled while 'Verify Assertion Signature' is enabled - this creates the injection vector.
  4. Verify Encryption Certificate configuration
    For each SAML Provider, open the provider settings, go to Advanced Protocol settings, and check if an Encryption Certificate is configured in the certificate field.
    Affected if Encryption Certificate is not configured or left empty in Advanced Protocol settings.

A user is affected if they run a vulnerable version AND have a SAML Provider with either (Verify Assertion Signature enabled AND Verify Response Signature disabled) OR no Encryption Certificate configured.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2025.8.6 / 2025.10.4 / 2025.12.4 or later
Fixed in 2025.8.62025.10.42025.12.4
Interim mitigation

Upgrade to authentik 2025.8.6, 2025.10.4, or 2025.12.4. Alternatively, ensure Verify Response Signature is enabled and Encryption Certificate is properly configured as temporary workarounds.

Recommended fix High confidence

Upgrade to Authentik 2025.8.6, 2025.10.4, or 2025.12.4 (or later stable release)

  1. Identify the current Authentik version running in your environment
  2. Confirm the version falls within an affected range: < 2025.8.6, >= 2025.10.0 and < 2025.10.4, or >= 2025.12.0 and < 2025.12.4
  3. Plan maintenance window for the upgrade
  4. Upgrade Authentik to version 2025.8.6, 2025.10.4, or 2025.12.4 (or a later stable release)
  5. After upgrade, verify SAML Source configurations: ensure 'Verify Response Signature' is enabled when 'Verify Assertion Signature' is enabled, and confirm 'Encryption Certificate' is properly configured under Advanced Protocol settings
  6. Test SAML authentication flows to confirm the fix is working and no regressions were introduced

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Authentik Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-25922 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-25922 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data