CVE-2026-27840: Github.com/zitadel/zitadel ZITADEL's Truncated Opaque Tokens Are Vulnerability

MODERATE
Advisory Identifier: GHSA-6mq3-xmgp-pjm5
CVSS 4.3
CWE-302
Published
Advisory Summary

CVE-2026-27840 is a MODERATE (CVSS 4.3) zitadel's truncated opaque tokens are vulnerability (CWE-302: Authentication Bypass by Assumed-Immutable Data) affecting Github.com/zitadel/zitadel libraries in the Go ecosystem. The issue involves zitadel's truncated opaque tokens are still valid. Remediation is available by upgrading affected packages to version 4.11.0, 3.4.7, 1.80.0-v2.20.0.20260216092519-feab8e1fa371.

CVE-2026-27840 at a Glance

CVE Identifier CVE-2026-27840
GHSA Identifier GHSA-6mq3-xmgp-pjm5
Severity MODERATE
CVSS v3.1 Base Score 4.3
CWE Classification CWE-302: Authentication Bypass by Assumed-Immutable Data
Affected Product Github.com/zitadel/zitadel
Package Ecosystem Go
Published Date
Last Updated

Security Impact

CVSS: 4.3

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:R/S:U/C:N/I:L/A:N).

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

How to Fix CVE-2026-27840

To remediate this vulnerability, upgrade all affected Github.com/zitadel/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.11.0
Upgrade github.com/zitadel/zitadel to 4.11.0
github.com/zitadel/zitadel fixed: 3.4.7
Upgrade github.com/zitadel/zitadel to 3.4.7
github.com/zitadel/zitadel fixed: Latest secure release
Upgrade github.com/zitadel/zitadel to Latest secure release
github.com/zitadel/zitadel fixed: 1.80.0-v2.20.0.20260216092519-feab8e1fa371
Upgrade github.com/zitadel/zitadel to 1.80.0-v2.20.0.20260216092519-feab8e1fa371
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-27840, inspect your project dependencies for Github.com/zitadel/zitadel:

inspect dependencies for github.com/zitadel/zitadel

Analyze the terminal output to locate any version of Github.com/zitadel/zitadel in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 4.11.0), 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-302: Authentication Bypass by Assumed-Immutable Data, where the authentication scheme or implementation uses key data elements that are assumed to be immutable, but can be controlled or modified by the attacker. In Github.com/zitadel/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 Opaque OIDC access tokens in v2 format, truncated to 80 characters are still considered valid. ZITADEL uses a symmetric AES encryption for opaque tokens. The cleartext payload is a concatenation of a couple of identifiers, such as a token ID and user ID. Internally Zitadel has 2 different versions of token payloads. v1 tokens are no longer created, but are still verified as to not invalidate existing session after upgrade. The cleartext payload has a format of `<token_id>:<user_id>`. v2 tokens distinguished further where the `token_id` is of the format `v2_<oidc_session_id>-at_<access_token_id>`. This is an example of such a cleartext: `V2_354201447279099906-at_354201447279165442:354201364702363650` ### Impact V1 token authZ/N session data is retrieved from the database using the (simple) `token_id` value and `user_id` value. The `user_id` (called `subject` in some parts of our code) was used as being the trusted user ID. V2 token authZ/N session data is retrieved from the database using the `oidc_session_id` and `access_token_id` and in this case the `user_id` from the token is ignored and taken from the session data in the database. By truncating the token to 80 chars, the user_id is now missing from the cleartext of the v2 token: `V2_354201447279099906-at_354201447279165442:` The back-end still accepts this for above reasons. This issue is not considered exploitable, but may look awkward when reproduced. ### Affected Versions All versions within the following ranges, including release candidates (RCs), are affected: - **v4.x**: `4.0.0` through `4.10.1` - **3.x**: `3.0.0` through `3.4.6` - **2.x**: `2.31.0` through `2.71.19` ### Patches The vulnerability has been addressed in the latest releases. The patch resolves the issue by verifying the `user_id` from the token against the session data from the database 4.x: Upgrade to >=[4.11.0](https://github.com/zitadel/zitadel/releases/tag/v4.11.0) 3.x: Update to >=[3.4.7](https://github.com/zitadel/zitadel/releases/tag/v3.4.7) 2.x: Update to >=[3.4.7](https://github.com/zitadel/zitadel/releases/tag/v3.4.7) ### Workarounds The recommended solution is to update ZITADEL to a patched version. ### Questions If there any questions or comments about this advisory, please send an email to [security@zitadel.com](mailto:security@zitadel.com) ### Credits ZITADEL thanks Olivier Becker and Lucas Dodgson for reporting this vulnerability.

CVE-2026-27840 Affected Github.com/zitadel/zitadel Versions

4 component(s)
Fixed Versions:
4.11.03.4.71.80.0-v2.20.0.20260216092519-feab8e1fa371
Product / Package Ecosystem Affected Versions Fixed Version
github.com/zitadel/zitadel
Go
≥ 4.0.0
< 4.11.0
4.11.0
github.com/zitadel/zitadel
Go
≥ 3.0.0
< 3.4.7
3.4.7
github.com/zitadel/zitadel
Go
≥ 2.31.0
≤ 2.71.19
github.com/zitadel/zitadel
Go
< 1.80.0-v2.20.0.20260216092519-feab8e1fa371
1.80.0-v2.20.0.20260216092519-feab8e1fa371

References

Frequently Asked Questions

What is CVE-2026-27840?
CVE-2026-27840 is a security vulnerability in Github.com/zitadel/zitadel involving ZITADEL's truncated opaque tokens are still valid under CWE-302: Authentication Bypass by Assumed-Immutable Data.
Which Github.com/zitadel/zitadel versions are affected?
Affected versions include releases prior to 4.11.0, 3.4.7, 1.80.0-v2.20.0.20260216092519-feab8e1fa371 across affected packages: github.com/zitadel/zitadel.
What version fixes CVE-2026-27840?
Upgrading to 4.11.0, 3.4.7, 1.80.0-v2.20.0.20260216092519-feab8e1fa371 (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.11.0, 3.4.7, Latest secure release, 1.80.0-v2.20.0.20260216092519-feab8e1fa371. Upgrade your dependency to 4.11.0, 3.4.7, Latest secure release, 1.80.0-v2.20.0.20260216092519-feab8e1fa371 or later.
What is the CVSS score of CVE-2026-27840?
CVE-2026-27840 has a CVSS v3.1 base score of 4.3 (MODERATE) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N.
What CWE is associated with CVE-2026-27840?
CVE-2026-27840 is classified under CWE-302: Authentication Bypass by Assumed-Immutable Data (The authentication scheme or implementation uses key data elements that are assumed to be immutable, but can be controlled or modified by the attacker.).
How can I check Go dependencies for CVE-2026-27840?
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-6mq3-xmgp-pjm5",
  "modified" : "2026-02-27T21:22:00Z",
  "published" : "2026-02-27T21:22:00Z",
  "aliases" : [ "CVE-2026-27840" ],
  "summary" : "ZITADEL's truncated opaque tokens are still valid",
  "details" : "### Summary\n\nOpaque OIDC access tokens in v2 format, truncated to 80 characters are still considered valid. \n\nZITADEL uses a symmetric AES encryption for opaque tokens. The cleartext payload is a concatenation of a couple of identifiers, such as a token ID and user ID. Internally Zitadel has 2 different versions of token payloads. v1 tokens are no longer created, but are still verified as to not invalidate existing session after upgrade.\n\nThe cleartext payload has a format of `<token_id>:<user_id>`. v2 tokens distinguished further where the `token_id` is of the format `v2_<oidc_session_id>-at_<access_token_id>`. This is an example of such a cleartext: `V2_354201447279099906-at_354201447279165442:354201364702363650`\n\n### Impact\n\nV1 token authZ/N session data is retrieved from the database using the (simple) `token_id` value and `user_id` value. The `user_id` (called `subject` in some parts of our code) was used as being the trusted user ID.\n\nV2 token authZ/N session data is retrieved from the database using the `oidc_session_id` and `access_token_id` and in this case the `user_id` from the token is ignored and taken from the session data in the database.\n\nBy truncating the token to 80 chars, the user_id is now missing from the cleartext of the v2 token: `V2_354201447279099906-at_354201447279165442:`  The back-end still accepts this for above reasons.\n\nThis issue is not considered exploitable, but may look awkward when reproduced.\n\n### Affected Versions\n\nAll versions within the following ranges, including release candidates (RCs), are affected:\n- **v4.x**: `4.0.0` through `4.10.1`\n- **3.x**: `3.0.0` through `3.4.6`\n- **2.x**: `2.31.0` through `2.71.19`\n\n### Patches\n\nThe vulnerability has been addressed in the latest releases. The patch resolves the issue by verifying the `user_id` from the token against the session data from the database\n\n4.x: Upgrade to >=[4.11.0](https://github.com/zitadel/zitadel/releases/tag/v4.11.0)\n3.x: Update to >=[3.4.7](https://github.com/zitadel/zitadel/releases/tag/v3.4.7)\n2.x: Update to >=[3.4.7](https://github.com/zitadel/zitadel/releases/tag/v3.4.7)\n\n### Workarounds\n\nThe recommended solution is to update ZITADEL to a patched version.\n\n### Questions\n\nIf there any questions or comments about this advisory, please send an email to [security@zitadel.com](mailto:security@zitadel.com)\n\n### Credits\n\nZITADEL thanks Olivier Becker and Lucas Dodgson for reporting this vulnerability.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/zitadel/zitadel"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "4.0.0"
      }, {
        "fixed" : "4.11.0"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/zitadel/zitadel"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "3.0.0"
      }, {
        "fixed" : "3.4.7"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/zitadel/zitadel"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "2.31.0"
      }, {
        "last_affected" : "2.71.19"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/zitadel/zitadel"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.80.0-v2.20.0.20260216092519-feab8e1fa371"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/zitadel/zitadel/security/advisories/GHSA-6mq3-xmgp-pjm5"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-27840"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/zitadel/zitadel/commit/feab8e1fa371f3ad654640fc869b2c14f2fdb602"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/zitadel/zitadel"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/zitadel/zitadel/releases/tag/v2.71.19"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/zitadel/zitadel/releases/tag/v3.4.7"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/zitadel/zitadel/releases/tag/v4.11.0"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-302" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-02-27T21:22:00Z",
    "nvd_published_at" : "2026-02-26T01:16:25Z"
  }
}