Authentication bypass via empty Source-stage POST
Published Jun 2, 2026 · Updated Jun 2, 2026
Improper authentication in authentik before 2025.12.6, 2026.2.4, and 2026.5.1 allows remote attackers to bypass a Source stage. An empty POST causes the Source stage to advance the flow without authenticating against the configured source. Exposure requires a reachable flow with a bound Source stage whose source exposes ui_login_button; exploitation skips authentication at that source.
Summary
What happened
Improper authentication in authentik before 2025.12.6, 2026.2.4, and 2026.5.1 allows remote attackers to bypass a Source stage. An empty POST causes the Source stage to advance the flow without authenticating against the configured source. Exposure requires a reachable flow with a bound Source stage whose source exposes ui_login_button; exploitation skips authentication at that source.
The record
- CVE
- CVE-2026-49448
- Published
- Jun 2, 2026
- Updated
- Jun 2, 2026
- Vendor
- Authentik Security Inc.
- Product
- authentik
- Classifications
- CWE-287, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 2, 2026CVE publishedPublication date reported by the CVE source.
- Jun 2, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 2025.12.6
- Affected versionversion=< 2026.2.4
- Affected versionversion=< 2026.5.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- Empty POST Source-stage bypassproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo