CVE-2026-94606: authentik: MFA Bypass via State Confusion / Parameter Injection in AuthenticatorEmailStage
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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
authentikto a version that resolves this vulnerability.Fixed in 2026.2.7 - Upgrade
Upgrade
authentikto a version that resolves this vulnerability.Fixed in 2026.5.7 - Upgrade
Upgrade
authentikto a version that resolves this vulnerability.Fixed in 2026.8.2
Event History
Frequently Asked Questions
Which accounts are realistically exposed to this issue?
Accounts are exposed when an attacker knows the target user's password and the target has not already enrolled the email authenticator factor. The impact is limited to email authenticator enrollment; other authenticator types are not affected.
What does an attacker need to do to exploit it?
The attacker must start or reach an email authenticator enrollment flow for the target account, supply an attacker-controlled recipient address in the setup request, and receive the one-time code sent to that address. Completing enrollment provides a session as the target and access to single sign-on applications behind that account.
Which releases contain the fix?
The issue is fixed in authentik versions 2026.2.7, 2026.5.7, and 2026.8.2. Versions before those listed fixed releases are affected.
What can be done if patching cannot happen immediately?
The provided information identifies un-enrolled email authenticator factors as the relevant exposure condition. No supported mitigation or configuration workaround is specified.