Quick answers
- Is CVE-2026-41569 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-41569 being exploited in the wild.
- How severe is CVE-2026-41569?
- Informational severity, with a CVSS score of 6.9, published 2 June 2026.
- Which products and versions are affected?
- Goauthentik Authentik < 2026.2.3, < 2025.12.5.
- Is there a fix for CVE-2026-41569?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-41569 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-41569?
- Check whether you run Goauthentik Authentik at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The WS-Federation provider in authentik used a raw string prefix check to validate the 'wreply' parameter instead of proper URL parsing. An attacker can bypass this check by providing a URL that starts with the legitimate domain but belongs to a different origin (e.g., https://portal.example.com.evil.tld/). When a victim uses a crafted login link, their browser will POST the signed WS-Federation response (wresult) to the attacker's infrastructure. This signed artifact can often be replayed to the legitimate application to impersonate the victim. The vulnerability is patched in versions 2026.2.3 and 2025.12.5.
Affected products
- goauthentik authentik < 2026.2.3, < 2025.12.5
Timeline
- 2026-05-12: advisory: GitHub advisory published by maintainers
- 2026-06-02: disclosed: CVE published to NVD