CVE-2026-41569
WS-Federation wreply Parameter Origin Validation Bypass in Authentik
Publication date: 2026-06-02
Last updated on: 2026-06-02
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| goauthentik | authentik | to 2026.2.3 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-601 | The web application accepts a user-controlled input that specifies a link to an external site, and uses that link in a redirect. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
The vulnerability exists in authentik, an open-source identity provider, specifically in its WS-Federation provider before version 2026.2.3. The issue is that the provider validates the user-supplied wreply parameter using a raw string prefix check instead of proper URL parsing.
An attacker can craft a login link with a wreply value that appears to be from a trusted origin but is actually from a malicious domain (for example, https://portal.example.com.evil.tld/). Because of the flawed validation, the victim's browser will send the signed WS-Federation login response to the attacker's infrastructure.
This can lead to the attacker receiving sensitive authentication tokens or information. The vulnerability was fixed in version 2026.2.3.
How can this vulnerability impact me? :
This vulnerability can allow an attacker to intercept authentication responses by tricking a user into clicking a specially crafted login link.
As a result, the attacker could potentially capture signed WS-Federation login responses, which may include sensitive authentication tokens or credentials.
This could lead to unauthorized access to user accounts or systems that rely on authentik for identity management.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, you should upgrade authentik to version 2026.2.3 or later, where the issue has been patched.