Vulnerability from bitnami_vulndb
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": [
{
"package": {
"ecosystem": "Bitnami",
"name": "authentik",
"purl": "pkg:bitnami/authentik"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "2026.2.7"
},
{
"introduced": "2026.5.0"
},
{
"fixed": "2026.5.7"
},
{
"introduced": "2026.8.0"
},
{
"fixed": "2026.8.2"
}
],
"type": "SEMVER"
}
],
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:L",
"type": "CVSS_V3"
}
]
}
],
"aliases": [
"CVE-2026-94606"
],
"database_specific": {
"cpes": [
"cpe:2.3:a:goauthentik:authentik:*:*:*:*:*:*:*:*"
],
"severity": "High"
},
"details": "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\u0027s 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.",
"id": "BIT-authentik-2026-94606",
"modified": "2026-10-01T09:55:18.588Z",
"published": "2026-10-01T09:23:05.728Z",
"references": [
{
"type": "WEB",
"url": "https://docs.goauthentik.io/releases/2026.2#fixed-in-202627"
},
{
"type": "WEB",
"url": "https://docs.goauthentik.io/releases/2026.5#fixed-in-202657"
},
{
"type": "WEB",
"url": "https://docs.goauthentik.io/releases/2026.8#fixed-in-202682"
},
{
"type": "WEB",
"url": "https://github.com/goauthentik/authentik/commit/01d4349f2aaa9beda532f92e2a251a17fefee9b3"
},
{
"type": "WEB",
"url": "https://github.com/goauthentik/authentik/commit/1fcf9868133e5d05e266edbc1f6f3ee972baa3f9"
},
{
"type": "WEB",
"url": "https://github.com/goauthentik/authentik/commit/c10ae83ebf8c61de2f1922edf1fab504d9f3b06f"
},
{
"type": "WEB",
"url": "https://github.com/goauthentik/authentik/commit/ec41732339726fba477182c0906a8d930b145beb"
},
{
"type": "WEB",
"url": "https://github.com/goauthentik/authentik/pull/25958"
},
{
"type": "WEB",
"url": "https://github.com/goauthentik/authentik/pull/25963"
},
{
"type": "WEB",
"url": "https://github.com/goauthentik/authentik/pull/25968"
},
{
"type": "WEB",
"url": "https://github.com/goauthentik/authentik/pull/25973"
},
{
"type": "WEB",
"url": "https://github.com/goauthentik/authentik/releases/tag/version/2026.2.7"
},
{
"type": "WEB",
"url": "https://github.com/goauthentik/authentik/releases/tag/version/2026.5.7"
},
{
"type": "WEB",
"url": "https://github.com/goauthentik/authentik/releases/tag/version/2026.8.2"
},
{
"type": "WEB",
"url": "https://github.com/goauthentik/authentik/security/advisories/GHSA-qgqp-xh8r-v73r"
},
{
"type": "WEB",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-94606"
}
],
"schema_version": "1.6.2",
"summary": "authentik: MFA Bypass via State Confusion / Parameter Injection in AuthenticatorEmailStage"
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.