Quick answers
- Is CVE-2026-49448 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-49448 being exploited in the wild.
- How severe is CVE-2026-49448?
- Critical severity, with a CVSS score of 9.8, published 2 June 2026.
- Which products and versions are affected?
- Goauthentik Authentik < 2025.12.6, < 2026.2.4, < 2026.5.1.
- Is there a fix for CVE-2026-49448?
- 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-49448 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-49448?
- 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
An authentication bypass vulnerability exists in authentik's SourceStage component. When the flow executor receives an empty POST request while the SourceStage is active, the 'SourceStageView.dispatch()' method fails to find a restore token and falls through to the base 'ChallengeStageView.post()' method. Because an empty data dictionary is considered valid by the challenge response logic, the system invokes 'stage_ok()' and advances the flow to the next stage (such as UserLoginStage) without requiring external identity provider verification. This allows a remote, unauthenticated attacker to bypass external authentication sources and gain access to user accounts. The issue is patched in versions 2025.12.6, 2026.2.4, and 2026.5.1.
Affected products
- goauthentik authentik < 2025.12.6, < 2026.2.4, < 2026.5.1
Timeline
- 2026-05-28: advisory: Vendor advisory published on GitHub
- 2026-06-02: disclosed: CVE published in NVD