Servers and applications
CVE-2026-41569
WS-Federation wreply origin bypass can exfiltrate signed login responses to attacker-controlled endpoints
- Severity
- Medium 6.9
- Published
- 12 May 2026
- Last changed
- 22 Jul 2026
- Added to UpHeron
- 1 Nov 2026
- Fixed in
- 2026.2.3
- Exploit chance
- 0.2% in the next 30 daysHigher than 7% of CVEs. EPSS by FIRST, 19 Nov 2026
- Weakness
- Open redirect (CWE-601)
- Attack
- Over the network · No login needed · No user action needed
- Attacker can
- Read some data · Change some data
- CVSS vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X- Also known as
- GHSA-995q-72cw-cfw3
- Sources
- NVD, Project advisories (GitHub)
Description
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.
The WS-Federation sign-in processor accepted any wreply whose string value started with the configured Reply URL, not correctly comparing the domain.
Once accepted, the attacker-controlled wreply is used as the autosubmit destination, and the victim's browser immediately POSTs the signed WS-Federation response (wresult) to that URL. The response is a valid signed authentication artifact; in many relying-party configurations it is replayable to the egitimate ACS endpoint, enabling victim impersonation in the target application.
Workarounds
Configure the WS-Federation provider's Reply URL with a specific path (e.g. https://portal.example.com/wsfed/acs) rather than a bare hostname. This prevents the host-extension bypass without patching, though upgrading is strongly preferred.
Affected software
| Software | Affected versions |
|---|---|
authentikServers and applications · cpe:a:goauthentik:authentik |
|
authentikServers and applications · github:goauthentik/authentik |
|
About authentik
The authentication glue you need.
- Total installations
- 1 millionauthentik
- GitHub stars
- 26,351GitHub, 15 Nov 2026
- Forks
- 2,134GitHub, 15 Nov 2026
- Latest release
- version/2026.8.5GitHub, 15 Nov 2026
- Released
- 21 Oct 2026GitHub
- First published on GitHub
- 30 Dec 2019GitHub
Release lines
| Release | Latest | Security fixes |
|---|---|---|
| 2026.8 | 2026.8.5 | Yes |
| 2026.5 | 2026.5.8 | Yes |
| 2026.2 | 2026.2.7 | Ended 18 Aug 2026 |
| 2025.12 | 2025.12.6 | Ended 22 May 2026 |
| 2025.10 | 2025.10.4 | Ended 24 Feb 2026 |
| 2025.8 | 2025.8.6 | Ended 13 Jan 2026 |
From endoflife.date.
Vulnerabilities in authentik
- In our list
- 48
- Published in the last 12 months
- 24
- Critical, last 12 months
- 3
- High, last 12 months
- 17
- Known exploited
- 0
- CVE-2026-94613Denial of Service via Malformed SAML MessagesHigh 7.5 9 Sept 2026
- CVE-2026-94611Certain stored credentials readable with view permission aloneHigh 8.1 9 Sept 2026
- CVE-2026-94612Authentication bypass in SAML Sources via assertion confusion and replayHigh 7.4 9 Sept 2026
- CVE-2026-94609Privilege escalation via delegated group and user managementHigh 8.8 9 Sept 2026
- CVE-2026-94606MFA bypass via recipient override in the email authenticatorHigh 8.9 9 Sept 2026
- GHSA-hmrg-vpp4-gj88Broken access control in Shared Signals Framework stream managementMedium 5.4 15 Jul 2026
References
- NVD https://nvd.nist.gov/vuln/detail/CVE-2026-41569
- CVE.org https://www.cve.org/CVERecord?id=CVE-2026-41569
- GitHub Advisory Database https://github.com/advisories/GHSA-995q-72cw-cfw3
- github.com https://github.com/goauthentik/authentik/security/advisories/GHSA-995q-72cw-cfw3