Vulnerabilities in pkg:golang/github.com/zitadel/zitadel
PACKAGECVE-2026-85056 is a HIGH (CVSS 8.2) mfa bypass vulnerability (General Security Weakness) affecting ZITADEL libraries in the Go ecosystem. The issue involves mfa bypass via session reuse in login v2. Remediation is available by upgrading affected packages to version 1.80.0-v2.20.0.20260717062356-56f4798ed31f.
pkg:golang/github.com/zitadel/zitadel
Vulnerability advisories affecting package pkg:golang/github.com/zitadel/zitadel. Select an advisory below to view technical details or fixes.
| Advisory ID | CVE / NVD | Severity | Summary |
|---|---|---|---|
| GHSA-9993-rfwp-rhwf | CVE-2026-85056 | HIGH | ZITADEL: MFA bypass via session reuse in Login V2 |
| GHSA-fgmf-7rf8-m6vf | CVE-2026-85057 | HIGH | ZITADEL: Actions V1 sandbox escape: host file read via require() |
| GHSA-v859-c572-qh5p | CVE-2026-76081 | MODERATE | ZITADEL: Improper Role Revocation on Granted Projects during Multiple Role Deletions |
| GHSA-vrh8-c9cm-wh8v | CVE-2026-56668 | HIGH | ZITADEL: Unauthorized Token Privilege Escalation in OAuth2 Token Exchange |
| GHSA-992q-9gwp-7r79 | CVE-2026-56666 | MODERATE | ZITADEL: Auto-linking by email: IdP-side email verification is not checked |
| GHSA-v77h-2w3m-94hx | CVE-2026-56665 | MODERATE | ZITADEL: Missing Token Expiration (`exp`) Validation in JWT IdP Provider |
| GHSA-jq8w-8q2f-ffm9 | CVE-2026-54693 | HIGH | ZITADEL Users Can Self-Verify Email/Phone via API |
| GHSA-wxg7-w2v3-w38g | CVE-2026-56664 | MODERATE | ZITADEL: Missing Token Lifecyle Validation (`exp` and `iat`) in JWT IdP Provider |
| GHSA-xqxv-4jc2-x56x | CVE-2026-55672 | HIGH | ZITADEL: Missing client_id binding in OIDC authorization code exchange and refresh token flows (RFC 6749 Section 4.1.3 violation) |
| GHSA-g5h5-m4hm-xjrr | CVE-2026-55669 | MODERATE | ZITADEL: Missing Token Audience Validation (`aud`) in JWT IdP Provider |
| GHSA-6x8v-2fq5-2229 | CVE-2026-55670 | LOW | ZITADEL: Cross-Tenant User Leakage via Recycled Identifiers |
| GHSA-29jh-8cfq-rr8x | CVE-2026-55671 | LOW | ZITADEL: Server-Side Request Forgery (SSRF) and Denylist Bypass in Outgoing HTTP Components |
| GHSA-rxvx-hhpj-q6px | CVE-2026-44671 | HIGH | ZITADEL has LDAP Filter Injection in Login Flow |
| GHSA-282g-fhmx-xf54 | CVE-2026-27946 | HIGH | ZITADEL Users Can Self-Verify Email/Phone via UpdateHumanUser API |
| GHSA-g2pf-ww5m-2r9m | CVE-2026-33132 | MODERATE | Zitadel is missing enforcement of organization scopes |
| GHSA-pr34-2v5x-6qjq | CVE-2026-29191 | CRITICAL | ZITADEL has 1-Click Account Takeover via XSS in /saml-post Endpoint |
| GHSA-pfrf-9r5f-73f5 | CVE-2026-29067 | HIGH | ZITADEL Vulnerable to Account Takeover Due to Improper Instance Validation in V2 Login |
| GHSA-6rx5-m2rc-hmf7 | CVE-2026-29192 | HIGH | ZITADEL: Stored XSS via Default URI Redirect Leads to Account Takeover |
| GHSA-25rw-g6ff-fmg8 | CVE-2026-29193 | HIGH | ZITADEL: Login V2 UI Policy Bypass Allows Unauthorized Self-Registration and Authentication |
| GHSA-6mq3-xmgp-pjm5 | CVE-2026-27840 | MODERATE | ZITADEL's truncated opaque tokens are still valid |
| GHSA-f4cf-9rvr-2rcx | CVE-2025-67717 | MODERATE | Zitadel Discloses the Total Number of Instance Users |
| GHSA-pvm5-9frx-264r | CVE-2026-23511 | MODERATE | Zitadel has a user enumeration vulnerability in Login UIs |
| GHSA-v959-qxv6-6f8p | CVE-2025-67495 | HIGH | ZITADEL Vulnerable to Account Takeover via DOM-Based XSS in Zitadel V2 Login |
| GHSA-7wfc-4796-gmg5 | CVE-2025-67494 | CRITICAL | ZITADEL Vulnerable to Unauthenticated Full-Read SSRF via V2 Login |
| GHSA-j4g7-v4m4-77px | CVE-2025-64717 | HIGH | ZITADEL is vulnerable to Account Takeover with deactivated Instance IdP |
| GHSA-cpf4-pmr4-w6cx | CVE-2025-64431 | HIGH | IDOR Vulnerabilities in ZITADEL's Organization API allows Cross-Tenant Data Tempering |
| GHSA-cfjq-28r2-4jv5 | CVE-2025-64103 | HIGH | Zitadel May Bypass Second Authentication Factor |
| GHSA-xrw9-r35x-x878 | CVE-2025-64102 | HIGH | Zitadel allows brute-forcing authentication factors |
| GHSA-6cf5-w9h3-4rqv | CVE-2024-49753 | MODERATE | Denied Host Validation Bypass in Zitadel Actions |
| GHSA-v333-7h2p-5fhv | CVE-2024-41953 | MODERATE | ZITADEL has improper HTML sanitization in emails and Console UI |
| GHSA-hfrg-4jwr-jfpj | CVE-2024-28855 | HIGH | Improper HTML sanitization in ZITADEL |
| GHSA-567v-6hmg-6qg7 | CVE-2024-41952 | MODERATE | ZITADEL "ignoring unknown usernames" vulnerability |
| GHSA-93m4-mfpg-c3xf | CVE-2025-48936 | HIGH | ZITADEL Allows Account Takeover via Malicious X-Forwarded-Proto Header Injection |
| GHSA-g4r8-mp7g-85fq | CVE-2025-46815 | HIGH | ZITADEL Allows IdP Intent Token Reuse |
| GHSA-f3gh-529w-v32x | CVE-2025-27507 | CRITICAL | IDOR Vulnerabilities in ZITADEL's Admin API that Primarily Impact LDAP Configurations |
| GHSA-hr5w-cwwq-2v4m | CVE-2024-29891 | HIGH | ZITADEL's Improper Content-Type Validation Leads to Account Takeover via Stored XSS + CSP Bypass |
| GHSA-mq4x-r2w3-j7mr | CVE-2024-28197 | HIGH | Account Takeover via Session Fixation in Zitadel [Bypassing MFA] |
| GHSA-7j7j-66cv-m239 | CVE-2024-32868 | HIGH | ZITADEL's Improper Lockout Mechanism Leads to MFA Bypass |
| GHSA-gp8g-f42f-95q2 | CVE-2024-29892 | HIGH | ZITADEL's actions can overload reserved claims |
| GHSA-3rmw-76m6-4gjc | CVE-2024-49757 | HIGH | User Registration Bypass in Zitadel |
| GHSA-cvw9-c57h-3397 | CVE-2024-39683 | MODERATE | ZITADEL Vulnerable to Session Information Leakage |
| GHSA-q5qj-x2h5-3945 | CVE-2024-32967 | MODERATE | Zitadel exposing internal database user name and host information |
| GHSA-2wmj-46rj-qm2w | CVE-2023-49097 | HIGH | ZITADEL Account Takeover via Malicious Host Header Injection |
| GHSA-7h8m-vrxx-vr4m | CVE-2023-47111 | HIGH | ZITADEL race condition in lockout policy execution |
| GHSA-v683-rcxx-vpff | CVE-2023-44399 | MODERATE | ZITADEL's password reset does not respect the "Ignoring unknown usernames" setting |
| GHSA-6rrr-78xp-5jp8 | CVE-2023-22492 | MODERATE | Zitadel RefreshToken invalidation vulnerability |
| GHSA-c8fj-4pm8-mp2c | CVE-2022-36051 | HIGH | Broken Authorization in ZITADEL Actions |
CVE-2026-85056 at a Glance
Security Impact
CVSS: 8.2
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N).
How to Fix CVE-2026-85056
To remediate this vulnerability, upgrade all affected ZITADEL dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
Upgrade github.com/zitadel/zitadel to 1.80.0-v2.20.0.20260717062356-56f4798ed31f
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
inspect dependencies for github.com/zitadel/zitadel
How to Check if You Are Affected
To determine whether your application is affected by CVE-2026-85056, inspect your project dependencies for ZITADEL:
inspect dependencies for github.com/zitadel/zitadel
Analyze the terminal output to locate any version of ZITADEL in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.80.0-v2.20.0.20260717062356-56f4798ed31f), your application is affected.
Note: Verify declared build manifests and deployed runtime container environments.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under General Security Weakness. In ZITADEL, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-85056 Affected ZITADEL Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
github.com/zitadel/zitadel
|
Go |
< 1.80.0-v2.20.0.20260717062356-56f4798ed31f
|
1.80.0-v2.20.0.20260717062356-56f4798ed31f
|
References
Frequently Asked Questions
What is CVE-2026-85056?
Which ZITADEL versions are affected?
What version fixes CVE-2026-85056?
Is github.com/zitadel/zitadel affected?
What is the CVSS score of CVE-2026-85056?
What CWE is associated with CVE-2026-85056?
How can I check Go dependencies for CVE-2026-85056?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-9993-rfwp-rhwf",
"modified" : "2026-09-24T18:19:35Z",
"published" : "2026-09-24T18:19:35Z",
"aliases" : [ "CVE-2026-85056" ],
"summary" : "ZITADEL: MFA bypass via session reuse in Login V2",
"details" : "### Summary\n\nA vulnerability in ZITADEL’s Login V2 UI allowed a password-verified browser session to be reused for a new authentication request without re-checking a user’s enrolled second factor (TOTP, OTP, or U2F). An attacker who already knows valid credentials can fully authenticate to an application without completing MFA.\n\n### Impact\n\nZITADEL Login V2 issues a session as soon as the user’s password is verified, before the MFA challenge is completed. If the MFA step is abandoned (for example by navigating back) and login is started again, Login V2 may reuse that existing session instead of requiring the second factor.\n\nSession validity checks only enforced MFA verification when the organization’s login policy had **Force MFA** (or **Force MFA for local users only**) enabled. They did not treat a voluntarily enrolled second factor as required. In the common case where MFA is available on the user but not organization-mandated, a password-only session was treated as fully authenticated and used to complete the OIDC or SAML callback, bypassing the user’s second factor.\n\n**Scope note:** This issue affects **customer applications** that authenticate users through the hosted **Login V2** UI (OIDC/SAML). It does **not** affect Login V1. It also does **not** affect authentication to ZITADEL itself — including the Console, the Management/Admin APIs, and user self-management — even when Login V2 is enabled.\n\n### Affected Versions\n\nSystems running one of the following versions are affected:\n\n* **4.x:** `4.0.0` through `4.16.0` (including RC versions)\n\n### Patches\n\nThe vulnerability has been addressed in the latest releases. The patch ensures Login V2 validates that any second factor enrolled on the user has been verified before an existing session can be reused to complete authentication.\n\n* **4.x**: Upgrade to $\\ge$ [4.16.1](https://github.com/zitadel/zitadel/releases/tag/v4.16.1)\n\n### Workarounds\n\nIf an immediate upgrade is not possible, enable **Force MFA** (or **Force MFA for local users only**, if you want to exempt IdP/federated logins) in the affected organization’s — or the instance default — login policy. This makes second-factor verification mandatory for password logins and closes this session-reuse bypass.\n\nNote that this is a broader policy change (MFA becomes mandatory for the scoped local logins) rather than a narrow fix limited to users who already self-enrolled a second factor.\n\n### Questions\n\nIf you have any questions or comments about this advisory, please email us at [security@zitadel.com](mailto:security@zitadel.com)\n\n### Credits\n\nThanks to Philippe Wechsler ([@MadMonkey87](https://github.com/MadMonkey87)) for finding and reporting the vulnerability.",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "Go",
"name" : "github.com/zitadel/zitadel"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "1.80.0-v2.20.0.20260717062356-56f4798ed31f"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/zitadel/zitadel/security/advisories/GHSA-9993-rfwp-rhwf"
}, {
"type" : "WEB",
"url" : "https://github.com/zitadel/zitadel/commit/049dbb25a56587fb3980c85c99819cad69f637db"
}, {
"type" : "WEB",
"url" : "https://github.com/zitadel/zitadel/commit/56f4798ed31fc1cfcd9a0e7f6f0152289d2fdc43"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/zitadel/zitadel"
}, {
"type" : "WEB",
"url" : "https://github.com/zitadel/zitadel/releases/tag/v4.16.1"
} ],
"database_specific" : {
"cwe_ids" : [ ],
"severity" : "HIGH",
"github_reviewed" : true,
"github_reviewed_at" : "2026-09-24T18:19:35Z",
"nvd_published_at" : null
}
}