dbcve.org
AuthentikApplication · Goauthentik

CVE-2026-41569

MEDIUM · 6.1 CVSS v3.1 Published 2026-06-02
Fix available
A fix is available. Upgrade to 2026.2.3 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 version 2026.2.3, the WS-Federation provider validates the user-supplied wreply parameter using a raw string prefix check rather than proper URL parsing. An attacker who can craft a login link can supply a wreply value on a different origin that passes the check (e.g. https://portal.example.com.evil.tld/), causing the victim's browser to POST the signed WS-Federation login response to attacker-controlled infrastructure. This issue has been patched in version 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 WS-Federation provider in authentik validates the wreply parameter using a raw string prefix check instead of proper URL parsing. An attacker can craft a login link with a malicious wreply value (e.g., https://portal.example.com.evil.tld/) that passes the flawed prefix validation, causing the victim's browser to POST the signed authentication response to attacker-controlled infrastructure.

MitigationUpgrade authentik to version 2026.2.3 or later which implements proper URL parsing validation for the wreply parameter.

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:< 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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 authentik installation
    Locate authentik installation by checking running containers (docker ps), process list (ps aux), or installed packages. Common installation methods include Docker, Kubernetes, or direct installation.
    Affected if authentik is installed and running
  2. Determine installed authentik version
    Check the running version via the admin UI (Settings > About page), API endpoint /api/v3/about/, or by inspecting container images (docker images) or package metadata.
    Affected if version is below 2026.2.3 (e.g., 2026.2.2, 2026.1.x, or earlier)
  3. Verify WS-Federation provider is configured
    Navigate to the authentik admin UI and check if any WS-Federation providers exist under the Identity Providers section, or query the API endpoint /api/v3/providers/wsfed/
    Affected if at least one WS-Federation provider is configured and active
  4. Inspect WS-Federation provider wreply configuration
    Review the configured wreply URLs in the WS-Federation provider settings. Look for any wreply values that may contain domains similar to but distinct from legitimate domains (e.g., subdomain variations like example.com.evil.tld).
    Affected if wreply URLs use loose validation that could allow look-alike domains to pass prefix checks

You are affected if running authentik version below 2026.2.3 AND you have a WS-Federation provider configured with a wreply URL that relies on the vulnerable raw string prefix validation.

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 2026.2.3 or later
Fixed in 2026.2.3
Interim mitigation

Upgrade authentik to version 2026.2.3 or later which implements proper URL parsing validation for the wreply parameter.

Recommended fix High confidence

2026.2.3

  1. 1. Back up your current Authentik installation and database before upgrading.
  2. 2. Consult the official Authentik upgrade documentation for your deployment method (docker, kubernetes, or package-based).
  3. 3. Pull or install Authentik version 2026.2.3 or later.
  4. 4. Run database migrations if required by the upgrade.
  5. 5. Verify the upgrade was successful by checking the Authentik admin interface version.
  6. 6. Test the WS-Federation provider functionality to confirm the wreply parameter is now properly validated using URL parsing.

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
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
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,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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