dbcve.org
AuthentikApplication · Goauthentik

CVE-2026-25748

HIGH · 7.5 CVSS v3.1 Published 2026-02-12
Fix available
A fix is available. Upgrade to 2025.10.4 / 2025.12.4 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 2025.10.4 and 2025.12.4, with a malformed cookie it was possible to bypass authentication when using forward authentication in the authentik Proxy Provider when used in conjunction with Traefik or Caddy as reverse proxy. When a malicious cookie was used, none of the authentik-specific X-Authentik-* headers were set which depending on application can grant access to an attacker. authentik 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

In authentik Proxy Provider with forward authentication (Traefik/Caddy), a malformed cookie bypasses authentication by preventing X-Authentik-* headers from being set, allowing unauthenticated access to protected applications.

MitigationUpgrade authentik to version 2025.10.4 or 2025.12.4 to patch the authentication bypass 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.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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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. Check installed authentik version
    For Docker deployments: run 'docker ps' to find the authentik container, then 'docker inspect <container_id>' to view the image tag. For other installs: check /version file or package manager.
    Affected if Version is less than 2025.10.4, or between 2025.12.0 and 2025.12.3 inclusive
  2. Identify if Proxy Provider is in use
    In the authentik admin UI, navigate to Applications > Providers. Look for providers of type 'Proxy Provider'. Note their names and configuration.
    Affected if One or more Proxy Provider instances exist in the environment
  3. Verify forward authentication mode is enabled
    For each Proxy Provider found, open its settings. Check if 'Forward authentication' or 'Trusted proxy' is enabled, and confirm the authentication mode is set to work with Traefik or Caddy (look for options referencing X-Authentik-* header forwarding).
    Affected if Forward authentication mode is enabled for Traefik or Caddy integration
  4. Confirm external auth flow configuration
    In the Proxy Provider settings, verify that the 'External host' points to a Traefik or Caddy instance, and that the provider is configured to pass X-Authentik-* headers to backend applications.
    Affected if External host is configured pointing to Traefik or Caddy with header forwarding enabled

Environment is affected if authentik version falls outside 2025.10.4+ or 2025.12.4+ AND a Proxy Provider with forward authentication for Traefik or Caddy is configured and in use.

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.10.4 / 2025.12.4 or later
Fixed in 2025.10.42025.12.4
Interim mitigation

Upgrade authentik to version 2025.10.4 or 2025.12.4 to patch the authentication bypass vulnerability.

Recommended fix High confidence

Authentik 2025.10.4 (for versions < 2025.10.4) or Authentik 2025.12.4 (for versions >= 2025.12.0 and < 2025.12.4)

  1. Identify the currently running Authentik version
  2. If running version < 2025.10.4, upgrade to Authentik 2025.10.4
  3. If running version >= 2025.12.0 and < 2025.12.4, upgrade to Authentik 2025.12.4
  4. After upgrade, verify that forward authentication with Proxy Provider works correctly and X-Authentik-* headers are properly set

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-25748 — 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-25748 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