Quick answers
- Is CVE-2026-41577 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-41577 being exploited in the wild.
- How severe is CVE-2026-41577?
- Informational severity, with a CVSS score of 6.9, published 2 June 2026.
- Which products and versions are affected?
- Goauthentik Authentik < 2025.12.5, < 2026.2.3.
- Is there a fix for CVE-2026-41577?
- 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-41577 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-41577?
- 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
A vulnerability exists in the SAML source response processor (specifically ResponseProcessor.parse()) of authentik due to insufficient verification of SAML assertion Conditions. The implementation ignores NotBefore, NotOnOrAfter, and AudienceRestriction elements. This lack of validation enables an attacker to perform replay attacks using expired assertions or to use assertions originally intended for a different service provider (SP) to authenticate to authentik. The issue is categorized as CWE-345 (Insufficient Verification of Data Authenticity) and has been addressed in versions 2025.12.5 and 2026.2.3.
Affected products
- goauthentik authentik < 2025.12.5, < 2026.2.3
Timeline
- 2026-05-12: advisory: GitHub Security Advisory published by maintainers
- 2026-06-02: disclosed: CVE published to NVD