{"id":"CVE-2026-94606","aliases":["BIT-authentik-2026-94606","EUVD-2026-86280","GHSA-qgqp-xh8r-v73r"],"status":"published","title":"authentik: MFA Bypass via State Confusion / Parameter Injection in AuthenticatorEmailStage","description":"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.","severity":{"version":"3.1","score":8.9,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:L","level":"high","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-10","score":0.00489,"percentile":0.42403,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-287","CWE-807"],"published":"2026-09-24T16:23:30Z","modified":"2026-10-28T02:30:23Z","fixes":[{"ecosystem":"Bitnami","package":"authentik","fixed_in":["2026.2.7","2026.5.7","2026.8.2"],"sources":["osv"]}],"affected":[{"source":"osv","ecosystem":"Bitnami","package":"authentik","ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"2026.2.7"},{"introduced":"2026.5.0"},{"fixed":"2026.5.7"},{"introduced":"2026.8.0"},{"fixed":"2026.8.2"}]}]}],"products":[{"vendor":"goauthentik","product":"authentik"}],"references":[{"url":"https://github.com/goauthentik/authentik/security/advisories/GHSA-qgqp-xh8r-v73r","tags":["x_refsource_CONFIRM","web","advisory"]},{"url":"https://github.com/goauthentik/authentik/pull/25958","tags":["x_refsource_MISC","web","fix"]},{"url":"https://github.com/goauthentik/authentik/pull/25963","tags":["x_refsource_MISC","web","fix"]},{"url":"https://github.com/goauthentik/authentik/pull/25968","tags":["x_refsource_MISC","web","fix"]},{"url":"https://github.com/goauthentik/authentik/pull/25973","tags":["x_refsource_MISC","web","fix"]},{"url":"https://github.com/goauthentik/authentik/commit/01d4349f2aaa9beda532f92e2a251a17fefee9b3","tags":["x_refsource_MISC","web","fix"]},{"url":"https://github.com/goauthentik/authentik/commit/1fcf9868133e5d05e266edbc1f6f3ee972baa3f9","tags":["x_refsource_MISC","web","fix"]},{"url":"https://github.com/goauthentik/authentik/commit/c10ae83ebf8c61de2f1922edf1fab504d9f3b06f","tags":["x_refsource_MISC","web","fix"]},{"url":"https://github.com/goauthentik/authentik/commit/ec41732339726fba477182c0906a8d930b145beb","tags":["x_refsource_MISC","web","fix"]},{"url":"https://docs.goauthentik.io/releases/2026.2#fixed-in-202627","tags":["x_refsource_MISC","web"]},{"url":"https://docs.goauthentik.io/releases/2026.5#fixed-in-202657","tags":["x_refsource_MISC","web"]},{"url":"https://docs.goauthentik.io/releases/2026.8#fixed-in-202682","tags":["x_refsource_MISC","web"]},{"url":"https://github.com/goauthentik/authentik/releases/tag/version/2026.2.7","tags":["x_refsource_MISC","web"]},{"url":"https://github.com/goauthentik/authentik/releases/tag/version/2026.5.7","tags":["x_refsource_MISC","web"]},{"url":"https://github.com/goauthentik/authentik/releases/tag/version/2026.8.2","tags":["x_refsource_MISC","web"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-94606","tags":["web","advisory"]},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/94xxx/CVE-2026-94606.json","tags":["advisory"]}],"sources":{"cve":[{"id":"CVE-2026-94606","title":"authentik: MFA Bypass via State Confusion / Parameter Injection in AuthenticatorEmailStage","description":"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.","status":"published","published":"2026-09-24T16:23:30.925Z","modified":"2026-10-05T15:33:40.648Z","cvss":[{"version":"3.1","score":8.9,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:L","level":"high","assessor":"cna"}],"cwes":["CWE-287","CWE-807"],"updated_at":"2026-11-02T14:19:53.786088Z"}],"euvd":[{"id":"EUVD-2026-86280","description":"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.","status":"published","published":"2026-09-24T16:23:30Z","modified":"2026-10-05T15:33:40Z","cvss":[{"version":"3.1","score":8.9,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:L","level":"high"}],"updated_at":"2026-11-02T17:27:39.819382Z"}],"nvd":[{"id":"CVE-2026-94606","description":"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.","status":"published","published":"2026-09-24T17:17:17.063Z","modified":"2026-10-05T16:17:17.863Z","cvss":[{"version":"3.1","score":8.9,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:L","level":"high","assessor":"secondary"}],"cwes":["CWE-287","CWE-807"],"updated_at":"2026-11-02T14:12:51.036099Z"}],"osv":[{"id":"CVE-2026-94606","title":"authentik: MFA Bypass via State Confusion / Parameter Injection in AuthenticatorEmailStage","description":"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.","status":"published","published":"2026-09-24T16:23:30.925Z","modified":"2026-10-28T02:30:23.571020782Z","cvss":[{"version":"3.1","score":8.9,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:L","level":"high"}],"cwes":["CWE-287","CWE-807"],"updated_at":"2026-11-02T15:45:20.931171Z"},{"id":"BIT-authentik-2026-94606","title":"authentik: MFA Bypass via State Confusion / Parameter Injection in AuthenticatorEmailStage","description":"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.","status":"published","published":"2026-10-01T09:23:05.728Z","modified":"2026-10-01T10:11:06.489220472Z","updated_at":"2026-11-02T15:28:28.70813Z"}]}}