Quick answers
- Is CVE-2026-94613 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-94613 being exploited in the wild.
- How severe is CVE-2026-94613?
- High severity, with a CVSS score of 7.5, published 24 September 2026.
- Which products and versions are affected?
- Authentik before 2026.2.7, 2026.5.7, and 2026.8.2.
- Is there a fix for CVE-2026-94613?
- 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-94613 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-94613?
- Check whether you run 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 malformed SAML message sent to endpoints serving the identity-provider or SAML source role triggers an unhandled exception that terminates the worker process. While sessions survive the crash due to database persistence, repeated attacks can sustain a denial of service against a fraction of traffic. The vulnerability is specific to SAML protocol implementations and requires network access to the affected endpoints.
Affected products
- authentik authentik before 2026.2.7, 2026.5.7, and 2026.8.2
Timeline
- 2026-09-24: disclosed