MFA bypass through email authenticator enrollment in goauthentik authentik

Note: This data is for reference and cybersecurity research purposes only.CyStack advises users not to use this information for unlawful purposes.

What is CVE-2026-94606?

CVE-2026-94606 is a vulnerability classified as Improper Authentication and Reliance on Untrusted Inputs in a Security Decision, affecting authentik (affected versions: < 2026.2.7, >= 2026.5.0, < 2026.5.7, and other affected versions). This vulnerability is rated High, with a CVSS score of 8.9. Current sources do not report this vulnerability as exploited.

Overview

Original source data

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 products and scope

  • authentik before 2026.2.7: affected.
  • authentik from 2026.5.0 through before 2026.5.7: affected.
  • authentik from 2026.8.0 through before 2026.8.2: affected.
  • Confirmed patched releases are 2026.2.7, 2026.5.7, and 2026.8.2.

The affected scope applies to deployments that enroll the email authenticator during an authentication or enrollment flow. The record does not establish the status of parallel or other branches outside these ranges.

Technical details

goauthentik authentik handles email authenticator enrollment during an authentication or enrollment flow by taking the recipient address from the setup request instead of using the address already established by the flow. Because the recipient address is taken from actor-controlled input, an actor who knows the target user's password can replace it with an address they control, receive the one-time code, and complete factor enrollment as the target.

The target must not have enrolled the email factor already. Completing enrollment creates a session as the target and can provide access to the single sign-on applications behind that account. The weakness falls under Improper Authentication and Reliance on Untrusted Inputs in a Security Decision. The public advisory describes the trust mismatch between the flow-established address and the request address, but does not disclose additional internal implementation details.

Exploitability

The issue is reachable over the network through an authentication or enrollment flow that uses the email authenticator. The actor must know the target user's password, but the record describes no additional application privilege or user interaction requirement; attack complexity is described as high. The target must also be without an existing email-factor enrollment.

The supplied record does not confirm exploitation in the wild and does not identify a public exploit. Whether the issue has been exploited outside the documented scenario is not established by the available evidence.

Technical impact

After enrollment is completed, the actor can obtain a session as the target user and access the single sign-on applications behind the account. Potential consequences include loss of confidentiality and integrity within the target account's permissions; the record does not describe a specific availability consequence.

The flaw does not provide the target password to the actor and instead requires that the actor already know it. The target must also lack an existing email-factor enrollment, and the deployment must use the email authenticator in the affected flow. Other authenticator types are not affected according to the advisory.

Business impact

If exploited, the actor can obtain a session as the target user and access the single sign-on applications protected by that account. Depending on the account's permissions, this could enable unauthorized access to data or changes in downstream applications, but the record does not confirm a specific breach scenario.

Exposure is limited to deployments that enroll the email authenticator during authentication or enrollment flows and to targets without an existing email-factor enrollment. Other authenticator types are outside the affected scope described by the advisory.

Remediation

  1. Upgrade authentik to the patched release for the deployed branch: 2026.2.7, 2026.5.7, or 2026.8.2. Use the patch release corresponding to the branch in service, and do not infer the status of other branches without confirmation.
  2. Until upgrading, do not rely on the email authenticator for multi-factor authentication. The advisory provides no workaround.
  3. Review accounts that enrolled the email factor while the deployment was running an affected release. If suspicious activity is found, handle sessions and factors under the organization's existing incident-response process; the public advisory does not define a separate recovery procedure.

Detection

  1. Inventory deployed authentik releases and compare them with the affected branches listed in affected_summary.
  2. Identify deployments that enable or use the email authenticator during authentication or enrollment flows.
  3. Review available authentik audit records and telemetry for unexpected email-factor enrollments, especially where the recorded recipient differs from the address established by the flow, if those fields are logged.
  4. Check accounts that completed email-factor enrollment while the deployment was running an affected release, where enrollment timing and flow information are available.

The advisory does not provide a specific IOC or log event. Monitoring for recipient mismatches is a precaution based on the failure mechanism, not a confirmed indicator.

Sources (21)
Learn more

Run an in-depth assessment with complete web risk management

CyStack VulnScan continuously discovers assets, validates vulnerabilities, and helps security teams prioritize remediation across the organization.