dbcve.org
AuthentikApplication · Goauthentik

CVE-2026-49448

CRITICAL · 9.8 CVSS v3.1 Published 2026-06-02
Fix available
A fix is available. Upgrade to 2025.12.6 / 2026.2.4 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit 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.6, 2026.2.4, and 2026.5.1, the Source stage can be bypassed by sending an empty POST. This issue has been patched in versions 2025.12.6, 2026.2.4, and 2026.5.1.

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 · moderate confidence

The Source stage in authentik's authentication flow can be bypassed by sending an empty POST request, allowing attackers to potentially circumvent authentication controls. This is an authentication bypass vulnerability in the identity provider's flow processing.

MitigationUpgrade authentik to version 2025.12.6, 2026.2.4, or 2026.5.1 or later to patch this vulnerability.

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.6>= 2026.2.0, < 2026.2.4>= 2026.5.0, < 2026.5.1

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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. Identify installed authentik version
    Log into the authentik admin interface and navigate to the About page (System -> Overview) to view the running version, or run 'docker ps' if using containers to check the image tag, or check the package manager if installed via pip/apt
    Affected if The displayed version falls into any of these ranges: < 2025.12.6 OR >= 2026.2.0 and < 2026.2.4 OR >= 2026.5.0 and < 2026.5.1
  2. Confirm Source stage is in use
    In the authentik admin interface, navigate to Flows and Stages (or API: /api/v3/core/flows/ and /api/v3/core/stages/) and identify if any flow uses a Source stage for authentication (such as SAML, OAuth, LDAP, or other external source stages)
    Affected if Any authentication flow is configured with a Source stage that handles user authentication via external identity providers
  3. Verify empty POST bypass is possible
    Send an empty POST request (with no body or parameters) to the Source stage endpoint used in your authentication flow - typically this would be an endpoint like /api/v3/core/sources/{source_type}/ or the flow executor endpoint for the flow containing the Source stage
    Affected if The request returns a successful authentication response or grants access without providing valid credentials, indicating the bypass is exploitable in your environment

You are affected if your authentik version is below 2025.12.6, between 2026.2.0-2026.2.4, or between 2026.5.0-2026.5.1 AND you have authentication flows using the Source stage.

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.6 / 2026.2.4 / 2026.5.1 or later
Fixed in 2025.12.62026.2.42026.5.1
Interim mitigation

Upgrade authentik to version 2025.12.6, 2026.2.4, or 2026.5.1 or later to patch this vulnerability.

Recommended fix High confidence

2026.5.1 (or 2026.2.4 for 2026.2.x branch, or 2025.12.6 for 2025.x branch)

  1. 1. Identify your current Authentik version by checking the running container image tag or docker-compose.yml
  2. 2. Determine which version branch you are on (2025.x, 2026.2.x, or 2026.5.x)
  3. 3. For 2025.x branch: upgrade to version 2025.12.6 or later
  4. 4. For 2026.2.x branch: upgrade to version 2026.2.4 or later
  5. 5. For 2026.5.x branch: upgrade to version 2026.5.1 or later
  6. 6. Update your Docker image tag or Helm chart values to the appropriate fixed version
  7. 7. Pull the new container image
  8. 8. Restart the Authentik containers/pods
Caveat Review Authentik release notes for any breaking changes between your current version and the target fixed version before upgrading

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

Fix this in Authentik Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
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,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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