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.
CVE-2026-94612
This high-severity CVE scores 7.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.4
- EG Score
- 7.4(low)
- EG Risk
- 33(Track)EG Risk 33/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity74% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
Published
September 24, 2026
Last Modified
September 24, 2026
Advisory Details (10)
Auto-updated Sep 24, 2026commit 984b0162711f (goauthentik/authentik)
Fix landed in goauthentik/authentik commit 984b0162711f — awaiting tagged release
https://github.com/goauthentik/authentik/commit/984b0162711f0d1988ed33544d0a671c93e4ec76commit 54fac864a0b3 (goauthentik/authentik)
Fix landed in goauthentik/authentik commit 54fac864a0b3 — awaiting tagged release
https://github.com/goauthentik/authentik/commit/54fac864a0b3bc00551af1908f662b3bf5cc6135commit 355d8cc3d755 (goauthentik/authentik)
Fix landed in goauthentik/authentik commit 355d8cc3d755 — awaiting tagged release
https://github.com/goauthentik/authentik/commit/355d8cc3d755fbba05fc5fa90ffbcbe6469acdddcommit 287ea13cdc23 (goauthentik/authentik)
Fix landed in goauthentik/authentik commit 287ea13cdc23 — awaiting tagged release
https://github.com/goauthentik/authentik/commit/287ea13cdc23c378abc20a7b71c9c7919a19a89asecurity: automated internal backport of patch 1914-saml.sec.patch to authentik-main
Fix merged in goauthentik/authentik PR #25972 on 2026-09-09 — awaiting tagged release
https://github.com/goauthentik/authentik/pull/25972security: automated internal backport of patch 1914-saml.sec.patch to authentik-2026.8
Fix merged in goauthentik/authentik PR #25967 on 2026-09-09 — awaiting tagged release
https://github.com/goauthentik/authentik/pull/25967security: automated internal backport of patch 1914-saml.sec.patch to authentik-2026.5
Fix merged in goauthentik/authentik PR #25962 on 2026-09-09 — awaiting tagged release
https://github.com/goauthentik/authentik/pull/25962security: automated internal backport of patch 1914-saml.sec.patch to authentik-2026.2
Fix merged in goauthentik/authentik PR #25957 on 2026-09-09 — awaiting tagged release
https://github.com/goauthentik/authentik/pull/25957Authentication bypass in SAML Sources via assertion confusion and replay · Advisory · goauthentik/authentik · GitHub
https://github.com/goauthentik/authentik/security/advisories/GHSA-cqj8-fxxf-9pg7Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 4× in last 7d / 4× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-24 18:36 UTCEG score recompute
- 2026-09-24 17:32 UTCEG score recompute
- 2026-09-24 16:27 UTCEG score recompute
- 2026-09-24 16:26 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(4)
What is CVE-2026-94612?
When was CVE-2026-94612 disclosed?
What is the CVSS score of CVE-2026-94612?
How do I remediate CVE-2026-94612?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-94612
Is Your Infrastructure Affected by CVE-2026-94612?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.