authentik: MFA Bypass via State Confusion / Parameter Injection in AuthenticatorEmailStage
21Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 8.9epss 0.5%
exploitation probability
0.5%top 61% of all CVEs
observed exploitation
nono source reports it
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.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:L
Affected products
goauthentik · authentikReferences
https://docs.goauthentik.io/releases/2026.2#fixed-in-202627https://docs.goauthentik.io/releases/2026.5#fixed-in-202657https://docs.goauthentik.io/releases/2026.8#fixed-in-202682https://github.com/goauthentik/authentik/commit/01d4349f2aaa9beda532f92e2a251a17fefee9b3https://github.com/goauthentik/authentik/commit/1fcf9868133e5d05e266edbc1f6f3ee972baa3f9https://github.com/goauthentik/authentik/commit/c10ae83ebf8c61de2f1922edf1fab504d9f3b06fhttps://github.com/goauthentik/authentik/commit/ec41732339726fba477182c0906a8d930b145bebhttps://github.com/goauthentik/authentik/pull/25958https://github.com/goauthentik/authentik/pull/25963https://github.com/goauthentik/authentik/pull/25968https://github.com/goauthentik/authentik/pull/25973https://github.com/goauthentik/authentik/releases/tag/version/2026.2.7