CVE-2026-56668: ZITADEL Unauthorized Token Privilege Escalation Vulnerability

HIGH
Advisory Identifier: GHSA-vrh8-c9cm-wh8v
CVSS 8.1
CWE-862
Published
Advisory Summary

CVE-2026-56668 is a HIGH (CVSS 8.1) unauthorized token privilege escalation vulnerability (CWE-862: Missing Authorization) affecting ZITADEL libraries in the Go ecosystem. The issue involves unauthorized token privilege escalation in oauth2 token exchange. Remediation is available by upgrading affected packages to version 4.15.3.

CVE-2026-56668 at a Glance

CVE Identifier CVE-2026-56668
GHSA Identifier GHSA-vrh8-c9cm-wh8v
Severity HIGH
CVSS v3.1 Base Score 8.1
CWE Classification CWE-862: Missing Authorization
Affected Product ZITADEL
Package Ecosystem Go
Published Date
Last Updated

Security Impact

CVSS: 8.1

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity High (I:H)
Availability None (A:N)

How to Fix CVE-2026-56668

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.

github.com/zitadel/zitadel fixed: 4.15.3
Upgrade github.com/zitadel/zitadel to 4.15.3
Verify Direct and Transitive Dependencies

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-56668, 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 4.15.3), 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 CWE-862: Missing Authorization, where the product does not perform an authorization check when an actor attempts to access a resource or perform an action. 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

### Summary A vulnerability in ZITADEL’s OAuth2 Token Exchange endpoint allows an authenticated user or client to exchange a low-privilege access token for a token with elevated permissions at a completely different application. This bypasses the intended authorization and separation policies configured within ZITADEL. ### Impact ZITADEL enables administrators to restrict token issuance based on client permissions, project roles, and specific scopes. Due to a missing verification step during the Token Exchange flow (`urn:ietf:params:oauth:grant-type:token-exchange`), ZITADEL fails to validate whether the incoming access token belongs to or is authorized for the client initiating the exchange. Additionally, ZITADEL does not enforce that the newly requested scopes must stay within the boundaries of the original token's scopes. An attacker with valid access to a low-privilege application can exploit this behavior by sending a token exchange request to a highly-privileged target application. This allows them to obtain administrative project roles, access sensitive profile data, or gain unauthorized access to other applications across the system. If public clients (which do not require client secrets) are used, this risk increases significantly as it requires no client authentication. ### Affected Versions Systems running one of the following versions are affected: * **4.x:** `4.0.0` through `4.15.2` (including RC versions) * **3.x:** `3.0.0` through `3.4.12` (including RC versions) ### Patches The vulnerability has been addressed in the latest releases. The patch resolves the issue by enforcing strict audience ownership verification and ensuring that requested scopes during a token exchange are restricted to a subset of the original token’s scopes. * **4.x**: Upgrade to $\ge$ [4.15.3](https://github.com/zitadel/zitadel/releases/tag/v4.15.3) * **3.x**: Upgrade to $\ge$ [4.15.3](https://github.com/zitadel/zitadel/releases/tag/v4.15.3) ### Workarounds The recommended solution is to upgrade to a patched version immediately. If an immediate upgrade is not possible, implement one of the following mitigations: - Disable via Feature Flag: Ensure the Token Exchange feature flag is explicitly turned off in your instance settings or environment variables (`ZITADEL_DEFAULTINSTANCE_FEATURES_TOKENEXCHANGE=false`). If the feature flag is disabled, the endpoint is unreachable and your system is not vulnerable. This is only possible in versions prior to v4.11.0, where the feature was not yet GA. - Remove the Grant Type: Ensure that the Token Exchange grant type is completely disabled or removed from all configured applications—especially high-privilege or public clients. ### Questions If you have any questions or comments about this advisory, please email us at [security@zitadel.com](mailto:security@zitadel.com). ### Credits Thanks to [thesecguy45](https://github.com/thesecguy45) and [Shubham Raj / Causal Security](https://github.com/cipher-creator) for reporting this vulnerability.

CVE-2026-56668 Affected ZITADEL Versions

1 component(s)
Fixed Versions:
4.15.3
Product / Package Ecosystem Affected Versions Fixed Version
github.com/zitadel/zitadel
Go
< 4.15.3
4.15.3

References

Frequently Asked Questions

What is CVE-2026-56668?
CVE-2026-56668 is a security vulnerability in ZITADEL involving Unauthorized Token Privilege Escalation in OAuth2 Token Exchange under CWE-862: Missing Authorization.
Which ZITADEL versions are affected?
Affected versions include releases prior to 4.15.3 across affected packages: github.com/zitadel/zitadel.
What version fixes CVE-2026-56668?
Upgrading to 4.15.3 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/zitadel/zitadel affected?
Yes, github.com/zitadel/zitadel is affected in releases prior to 4.15.3. Upgrade your dependency to 4.15.3 or later.
What is the CVSS score of CVE-2026-56668?
CVE-2026-56668 has a CVSS v3.1 base score of 8.1 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N.
What CWE is associated with CVE-2026-56668?
CVE-2026-56668 is classified under CWE-862: Missing Authorization (The product does not perform an authorization check when an actor attempts to access a resource or perform an action.).
How can I check Go dependencies for CVE-2026-56668?
Run the dependency tree command: 'inspect dependencies for github.com/zitadel/zitadel'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-vrh8-c9cm-wh8v",
  "modified" : "2026-09-14T21:28:23Z",
  "published" : "2026-09-14T21:28:23Z",
  "aliases" : [ "CVE-2026-56668" ],
  "summary" : "ZITADEL: Unauthorized Token Privilege Escalation in OAuth2 Token Exchange",
  "details" : "### Summary\n\nA vulnerability in ZITADEL’s OAuth2 Token Exchange endpoint allows an authenticated user or client to exchange a low-privilege access token for a token with elevated permissions at a completely different application. This bypasses the intended authorization and separation policies configured within ZITADEL.\n\n### Impact\n\nZITADEL enables administrators to restrict token issuance based on client permissions, project roles, and specific scopes. Due to a missing verification step during the Token Exchange flow (`urn:ietf:params:oauth:grant-type:token-exchange`), ZITADEL fails to validate whether the incoming access token belongs to or is authorized for the client initiating the exchange. Additionally, ZITADEL does not enforce that the newly requested scopes must stay within the boundaries of the original token's scopes.\n\nAn attacker with valid access to a low-privilege application can exploit this behavior by sending a token exchange request to a highly-privileged target application. This allows them to obtain administrative project roles, access sensitive profile data, or gain unauthorized access to other applications across the system. If public clients (which do not require client secrets) are used, this risk increases significantly as it requires no client authentication.\n\n### Affected Versions\n\nSystems running one of the following versions are affected:\n\n* **4.x:** `4.0.0` through `4.15.2` (including RC versions)\n* **3.x:** `3.0.0` through `3.4.12` (including RC versions)\n\n### Patches\n\nThe vulnerability has been addressed in the latest releases. The patch resolves the issue by enforcing strict audience ownership verification and ensuring that requested scopes during a token exchange are restricted to a subset of the original token’s scopes.\n\n* **4.x**: Upgrade to $\\ge$ [4.15.3](https://github.com/zitadel/zitadel/releases/tag/v4.15.3)\n* **3.x**: Upgrade to $\\ge$ [4.15.3](https://github.com/zitadel/zitadel/releases/tag/v4.15.3)\n\n### Workarounds\n\nThe recommended solution is to upgrade to a patched version immediately. If an immediate upgrade is not possible, implement one of the following mitigations:\n - Disable via Feature Flag: Ensure the Token Exchange feature flag is explicitly turned off in your instance settings or environment variables (`ZITADEL_DEFAULTINSTANCE_FEATURES_TOKENEXCHANGE=false`). If the feature flag is disabled, the endpoint is unreachable and your system is not vulnerable. This is only possible in versions prior to v4.11.0, where the feature was not yet GA.\n- Remove the Grant Type: Ensure that the Token Exchange grant type is completely disabled or removed from all configured applications—especially high-privilege or public clients.\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 [thesecguy45](https://github.com/thesecguy45) and [Shubham Raj / Causal Security](https://github.com/cipher-creator) for reporting this vulnerability.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/zitadel/zitadel"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "4.15.3"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/zitadel/zitadel/security/advisories/GHSA-vrh8-c9cm-wh8v"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-56668"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/zitadel/zitadel/commit/e2886a61670ca8fd41c9434f87036546e5620bcc"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/zitadel/zitadel"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/zitadel/zitadel/releases/tag/v4.15.3"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-862" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-09-14T21:28:23Z",
    "nvd_published_at" : "2026-07-10T18:16:24Z"
  }
}