Skip to content
Fencer Vulns
high 8.9

CVE-2026-94606 json

authentik: MFA Bypass via State Confusion / Parameter Injection in AuthenticatorEmailStage

published 2026-09-24 45 d ago modified 2026-10-05 34 d ago also BIT-authentik-2026-94606 , EUVD-2026-86280 , GHSA-qgqp-xh8r-v73r

cvss
8.9
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.5%
EPSS 0.5% chance of exploitation in 30 days, percentile 42%
public exploits
0
none known

Summary

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.

Patch / fix

  • bitnami authentik 2026.2.7, 2026.5.7, 2026.8.2
  • goauthentik authentik 2026.2.7, 2026.5.7, 2026.8.2

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
34 d ago

Exploit prediction

0.49% chance of exploitation in the next 30 days, higher than 42% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 8.9 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:L
OSV 3.1 8.9 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:L

Affected packages

ecosystem package affected fixed in
bitnami authentik
<2026.2.7
>=2026.5.0, <2026.5.7
>=2026.8.0, <2026.8.2
2026.2.7
2026.5.7
2026.8.2

Affected products

  • goauthentik authentik

Classification

Weakness
  • CWE-287 Improper Authentication
  • CWE-807 Reliance on Untrusted Inputs in a Security Decision

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.