authentik is an open-source identity provider. Prior to 2026.2.7, 2026.5.7, and 2026.8.2, authentik email authenticator enrollment during an authentication or enrollment flow accepts a recipient address supplied in the setup request instead of using the address already established by the flow. An actor who knows a target user's password can substitute an attacker-controlled address, receive the one-time code, and finish enrolling the factor as the target. The target must not have enrolled the email factor already. Successful enrollment gives the actor a session as the target and access to single sign-on applications behind the account. Other authenticator types are not affected. This issue is fixed in versions 2026.2.7, 2026.5.7, and 2026.8.2.
CVE-2026-94606
This high-severity CVE scores 8.9 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
- 8.9
- EG Score
- 8.9(low)
- EG Risk
- 45(Track)EG Risk 45/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 computedSeverity89% × 45%Exploitation0% × 40%Automatability30% × 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 ec4173233972 (goauthentik/authentik)
Fix landed in goauthentik/authentik commit ec4173233972 — awaiting tagged release
https://github.com/goauthentik/authentik/commit/ec41732339726fba477182c0906a8d930b145bebcommit c10ae83ebf8c (goauthentik/authentik)
Fix landed in goauthentik/authentik commit c10ae83ebf8c — awaiting tagged release
https://github.com/goauthentik/authentik/commit/c10ae83ebf8c61de2f1922edf1fab504d9f3b06fcommit 1fcf9868133e (goauthentik/authentik)
Fix landed in goauthentik/authentik commit 1fcf9868133e — awaiting tagged release
https://github.com/goauthentik/authentik/commit/1fcf9868133e5d05e266edbc1f6f3ee972baa3f9commit 01d4349f2aaa (goauthentik/authentik)
Fix landed in goauthentik/authentik commit 01d4349f2aaa — awaiting tagged release
https://github.com/goauthentik/authentik/commit/01d4349f2aaa9beda532f92e2a251a17fefee9b3security: automated internal backport of patch 2032-authenticator-email-recipient-override.sec.patch to authentik-main
Fix merged in goauthentik/authentik PR #25973 on 2026-09-09 — awaiting tagged release
https://github.com/goauthentik/authentik/pull/25973security: automated internal backport of patch 2032-authenticator-email-recipient-override.sec.patch to authentik-2026.8
Fix merged in goauthentik/authentik PR #25968 on 2026-09-09 — awaiting tagged release
https://github.com/goauthentik/authentik/pull/25968security: automated internal backport of patch 2032-authenticator-email-recipient-override.sec.patch to authentik-2026.5
Fix merged in goauthentik/authentik PR #25963 on 2026-09-09 — awaiting tagged release
https://github.com/goauthentik/authentik/pull/25963security: automated internal backport of patch 2032-authenticator-email-recipient-override.sec.patch to authentik-2026.2
Fix merged in goauthentik/authentik PR #25958 on 2026-09-09 — awaiting tagged release
https://github.com/goauthentik/authentik/pull/25958MFA bypass via recipient override in the email authenticator · Advisory · goauthentik/authentik · GitHub
https://github.com/goauthentik/authentik/security/advisories/GHSA-qgqp-xh8r-v73rWeakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 3× in last 7d / 3× 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 17:33 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-94606?
When was CVE-2026-94606 disclosed?
What is the CVSS score of CVE-2026-94606?
How do I remediate CVE-2026-94606?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-94606
Is Your Infrastructure Affected by CVE-2026-94606?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.