CVE-2026-94612: authentik: Authentication bypass via assertion confusion in SAML sources
Noroxi assessment
Priority: Monitor (action score 29/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.26% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
- No fixed version is recorded, but the references include a patch (commit or PR) link.
Low priority for now. See the fix and affected versions sections below.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
authentik is an open-source identity provider. Prior to 2026.2.7, 2026.5.7, and 2026.8.2, an authentik SAML Source verifies an assertion's signature and validity period but does not ensure that the identity provider issued the assertion for that Source or in response to a login request from that Source. The SAML Source also does not record already accepted assertions, allowing replay. An unauthenticated actor who possesses such a valid assertion can use an assertion intended for another service provider or reuse an earlier assertion to authenticate as the user named by the assertion. Only SAML Sources are affected; SAML Providers and other Source types are not affected. This issue is fixed in versions 2026.2.7, 2026.5.7, and 2026.8.2.
- Published
- Sep 24, 2026
- Updated
- Sep 24, 2026
- EPSS
- 0.2% · 19th percentile
- CWE
- CWE-287
Report tools
Action score
29
Low priority for now.
- CVSS
- 29 / 40 · 7.4 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · GitHub_M
- 7.4
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
goauthentik authentik
- < 2026.2.7, >= 2026.5.0, < 2026.5.7, >= 2026.8.0, < 2026.8.2affected
Same product
goauthentik: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-49448authentik: SourceStage bypass via empty POST39Monitor
- CVE-2024-38371Insufficient access control for OAuth2 Device Code flow in authentik39Monitor
- CVE-2023-48228OAuth2: PKCE can be fully circumvented39Monitor
Published before and after this one in the same product
- ← EarlierCVE-2026-61574Aug 18, 2026 · authentik RAC: access any endpoint via an unrelated application35Monitor
- ← EarlierCVE-2026-94611Sep 24, 2026 · authentik: Stored credentials are readable with view permission alone32Monitor
- Later →CVE-2026-94606Sep 24, 2026 · authentik: MFA Bypass via State Confusion / Parameter Injection in AuthenticatorEmailStage35Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-49448114 days apartauthentik: SourceStage bypass via empty POST39Monitor
- CVE-2026-946060 days apartauthentik: MFA Bypass via State Confusion / Parameter Injection in AuthenticatorEmailStage35Monitor
- CVE-2026-49443114 days apartauthentik: `UserSourceConnection.user` and `GroupSourceConnection.group` are changeable through the API35Monitor
- CVE-2026-25922224 days apartauthentik has a Signature Verification Bypass via SAML Assertion Wrapping35Monitor
- CVE-2026-25748224 days apartauthentik has a forward authentication bypass with broken cookie30Monitor
- CVE-2025-52553454 days apartauthentik has Insufficient Session verification for Remote Access Control endpoint access22Monitor
Not on record for this CVE: researcher credit · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- none
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- None
Weakness class (CWE)
CWE-287 · Improper AuthenticationCVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
nvd-secondary
Root cause
Authentication is added route by route instead of being enforced in one place. When a route added later bypasses the shared middleware, the session check never runs for it.
The bug in code
The whole CWE-287 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
app.use("/admin", requireSession, adminRouter);
// Route added later skips the middleware
app.post("/admin-api/config", updateConfig);Fixed
const admin = express.Router();
admin.use(requireSession, requireRole("admin"));
admin.post("/config", updateConfig);
app.use("/admin", admin);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Authentication AbuseCAPEC-114Medium
- Authentication BypassCAPEC-115Medium
- Identity SpoofingCAPEC-151likelihood: Medium · Medium
- Fake the Source of DataCAPEC-194Medium
- Exploiting Trust in ClientCAPEC-22likelihood: High · High
- Utilizing REST's Trust in the System Resource to Obtain Sensitive DataCAPEC-57likelihood: Medium · Very High
- Session HijackingCAPEC-593likelihood: High · Very High
- Token ImpersonationCAPEC-633Medium
ATT&CK techniques
Change log (0)
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Show all references (14 more)Show less
- docs.goauthentik.io/releases/2026.5#fixed-in-202657
- docs.goauthentik.io/releases/2026.8#fixed-in-202682
- github.com/goauthentik/authentik/commit/287ea13cdc23c378abc20a7b71c9c7919a19a89a
- github.com/goauthentik/authentik/commit/355d8cc3d755fbba05fc5fa90ffbcbe6469acddd
- github.com/goauthentik/authentik/commit/54fac864a0b3bc00551af1908f662b3bf5cc6135
- github.com/goauthentik/authentik/commit/984b0162711f0d1988ed33544d0a671c93e4ec76
- github.com/goauthentik/authentik/pull/25957
- github.com/goauthentik/authentik/pull/25962
- github.com/goauthentik/authentik/pull/25967
- github.com/goauthentik/authentik/pull/25972
- github.com/goauthentik/authentik/releases/tag/version/2026.2.7
- github.com/goauthentik/authentik/releases/tag/version/2026.5.7
- github.com/goauthentik/authentik/releases/tag/version/2026.8.2
- github.com/goauthentik/authentik/security/advisories/GHSA-cqj8-fxxf-9pg7
Vendor advisories and official records. Exploit/PoC links are deliberately left out.