dbcve.org
AuthentikApplication · Goauthentik

CVE-2026-41577

HIGH · 7.5 CVSS v3.1 Published 2026-06-02
Fix available
A fix is available. Upgrade to 2025.12.5 / 2026.2.3 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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 versions 2025.12.5 and 2026.2.3, the SAML source response processor (ResponseProcessor.parse()) does not validate the Conditions element on assertions. NotBefore, NotOnOrAfter, and AudienceRestriction are all ignored. This allows replay of expired assertions and acceptance of assertions intended for other service providers. This issue has been patched in versions 2025.12.5 and 2026.2.3.

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

The SAML source response processor in authentik fails to validate the Conditions element in SAML assertions, specifically ignoring NotBefore, NotOnOrAfter timing constraints and AudienceRestriction. This allows attackers to replay expired assertions or use assertions intended for other service providers, enabling authentication bypass.

MitigationUpgrade to authentik versions 2025.12.5 or 2026.2.3 which contain the patch for proper Conditions element validation.

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.12.5>= 2026.2.0, < 2026.2.3

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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

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

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. Identify installed authentik version
    Check the version via the authentik admin UI under 'About' page, or via command line with 'docker ps' for container image tag, or 'pip show authentik' if installed via pip
    Affected if Version is < 2025.12.5 OR (>= 2026.2.0 AND < 2026.2.3)
  2. Determine if SAML sources are configured
    In authentik admin UI, navigate to 'Providers' and look for providers of type 'SAML Source', or use the API endpoint /api/v3/core/providers/ to list providers and filter for SAML source type
    Affected if Any SAML source provider exists in the environment
  3. Verify the SAML response processing pipeline
    The vulnerability lies in the SAML source response processor which handles incoming assertions. This is an internal component; confirm by reviewing authentik version first. If a SAML source is configured and the version is affected, the Conditions element validation is bypassed
    Affected if Running an affected version AND at least one SAML source provider is configured

You are affected if your authentik version is < 2025.12.5 or between 2026.2.0 and 2026.2.3 inclusive, AND you have at least one SAML source provider configured in your environment.

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.12.5 / 2026.2.3 or later
Fixed in 2025.12.52026.2.3
Interim mitigation

Upgrade to authentik versions 2025.12.5 or 2026.2.3 which contain the patch for proper Conditions element validation.

Recommended fix High confidence

2025.12.5 (for 2025.x branches) or 2026.2.3 (for 2026.x branches)

  1. Backup your Authentik instance and database before upgrading
  2. Identify your current Authentik version by checking the running container or installation
  3. If running version 2025.x: upgrade to version 2025.12.5 or later
  4. If running version 2026.2.x: upgrade to version 2026.2.3 or later
  5. For containerized deployments: pull the new image (e.g., authentik/server:2025.12.5 or authentik/server:2026.2.3) and restart
  6. For source installations: follow the standard upgrade procedure for your installation method
  7. After upgrade, verify the SAML source configuration and test authentication flows

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
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-41577 — 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-41577 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