CVE-2026-56664: ZITADEL Missing Token Lifecyle Validation (`exp` Vulnerability

MODERATE
Advisory Identifier: GHSA-wxg7-w2v3-w38g
CVSS 4.2
CWE-613
Published
Advisory Summary

CVE-2026-56664 is a MODERATE (CVSS 4.2) missing token lifecyle validation (`exp` vulnerability (CWE-613: Insufficient Session Expiration) affecting ZITADEL libraries in the Go ecosystem. The issue involves missing token lifecyle validation (`exp` and `iat`) in jwt idp provider. Remediation is available by upgrading affected packages to version 1.80.0-v2.20.0.20260615122908-fad02c6d9f45.

CVE-2026-56664 at a Glance

CVE Identifier CVE-2026-56664
GHSA Identifier GHSA-wxg7-w2v3-w38g
Severity MODERATE
CVSS v3.1 Base Score 4.2
CWE Classification CWE-613: Insufficient Session Expiration
Affected Product ZITADEL
Package Ecosystem Go
Published Date
Last Updated

Security Impact

CVSS: 4.2

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

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

How to Fix CVE-2026-56664

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: 1.80.0-v2.20.0.20260615122908-fad02c6d9f45
Upgrade github.com/zitadel/zitadel to 1.80.0-v2.20.0.20260615122908-fad02c6d9f45
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-56664, 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.20260615122908-fad02c6d9f45), 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-613: Insufficient Session Expiration, where according to wasc, "insufficient session expiration is when a web site permits an attacker to reuse old session credentials or session ids for authorization.". 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 token lifecycle validation vulnerability was discovered in ZITADEL's external JWT Identity Provider (IdP) implementation. ZITADEL enforces a 1-hour maximum token age freshness window (`maxAge`) calculated from the token's issue time. However, this safety check is guarded by a presence condition. If an incoming token omits the `iat` claim, the freshness check is entirely bypassed, allowing arbitrarily old tokens to pass authentication successfully. Per the OIDC Core 1.0 specification, identity token validation pipelines must strictly handle and enforce session expiration. ZITADEL's silent acceptance of tokens missing these temporal constraints compromises session integrity. ### Impact An attacker in possession of a stale token lacking an `iat` claim can reuse it indefinitely without triggering the maximum age freshness invalidation. ### Affected Versions Systems running one of the following versions are affected: * **4.x**: `4.0.0` through `4.15.1` (including RC versions) * **3.x**: `3.0.0` through `3.4.11` (including RC versions) ### Patches The vulnerability has been addressed in the latest releases. ZITADEL now explicitly rejects tokens that lack an `iat` claim. * **4.x**: Upgrade to $\ge$ [4.15.2](https://github.com/zitadel/zitadel/releases/tag/v4.15.2) * **3.x**: Upgrade to $\ge$ [3.4.12](https://github.com/zitadel/zitadel/releases/tag/v3.4.12) ### Workarounds The recommended solution is to update ZITADEL to a patched version. If an immediate upgrade is not feasible, ensure at the upstream Identity Provider level that your external IdP explicitly includes the `iat` claim in all signed JWTs. ### Publication Note This advisory covers a subset of the security issues originally published on ZITADEL's registry under this tracking ID. To adhere strictly to CVE formatting standards regarding independently fixable flaws, the original "Token Lifecycle Validation" disclosure has been split into two granular entries. This entry specifically tracks the missing `iat` claim logic, while a separate companion entry tracks the missing `exp` claim logic: [GHSA-v77h-2w3m-94hx](https://github.com/zitadel/zitadel/security/advisories/GHSA-v77h-2w3m-94hx) ### 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 [Android-Login-Analysis](https://github.com/Android-Login-Analysis), Jason Zhou and [Pedro Giglioti](https://github.com/Punisher100) for reporting this vulnerability.

CVE-2026-56664 Affected ZITADEL Versions

1 component(s)
Fixed Versions:
1.80.0-v2.20.0.20260615122908-fad02c6d9f45
Product / Package Ecosystem Affected Versions Fixed Version
github.com/zitadel/zitadel
Go
< 1.80.0-v2.20.0.20260615122908-fad02c6d9f45
1.80.0-v2.20.0.20260615122908-fad02c6d9f45

References

Frequently Asked Questions

What is CVE-2026-56664?
CVE-2026-56664 is a security vulnerability in ZITADEL involving Missing Token Lifecyle Validation (`exp` and `iat`) in JWT IdP Provider under CWE-613: Insufficient Session Expiration.
Which ZITADEL versions are affected?
Affected versions include releases prior to 1.80.0-v2.20.0.20260615122908-fad02c6d9f45 across affected packages: github.com/zitadel/zitadel.
What version fixes CVE-2026-56664?
Upgrading to 1.80.0-v2.20.0.20260615122908-fad02c6d9f45 (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 1.80.0-v2.20.0.20260615122908-fad02c6d9f45. Upgrade your dependency to 1.80.0-v2.20.0.20260615122908-fad02c6d9f45 or later.
What is the CVSS score of CVE-2026-56664?
CVE-2026-56664 has a CVSS v3.1 base score of 4.2 (MODERATE) with vector string CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N.
What CWE is associated with CVE-2026-56664?
CVE-2026-56664 is classified under CWE-613: Insufficient Session Expiration (According to WASC, "Insufficient Session Expiration is when a web site permits an attacker to reuse old session credentials or session IDs for authorization.").
How can I check Go dependencies for CVE-2026-56664?
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-wxg7-w2v3-w38g",
  "modified" : "2026-07-18T17:24:09Z",
  "published" : "2026-06-18T13:52:21Z",
  "aliases" : [ "CVE-2026-56664" ],
  "summary" : " ZITADEL: Missing Token Lifecyle Validation (`exp` and `iat`) in JWT IdP Provider",
  "details" : "### Summary\n\nA token lifecycle validation vulnerability was discovered in ZITADEL's external JWT Identity Provider (IdP) implementation.\nZITADEL enforces a 1-hour maximum token age freshness window (`maxAge`) calculated from the token's issue time. However, this safety check is guarded by a presence condition. If an incoming token omits the `iat` claim, the freshness check is entirely bypassed, allowing arbitrarily old tokens to pass authentication successfully.\n\nPer the OIDC Core 1.0 specification, identity token validation pipelines must strictly handle and enforce session expiration. ZITADEL's silent acceptance of tokens missing these temporal constraints compromises session integrity.\n\n### Impact\n\nAn attacker in possession of a stale token lacking an `iat` claim can reuse it indefinitely without triggering the maximum age freshness invalidation.\n\n### Affected Versions\n\nSystems running one of the following versions are affected:\n\n* **4.x**: `4.0.0` through `4.15.1` (including RC versions)\n* **3.x**: `3.0.0` through `3.4.11` (including RC versions)\n\n### Patches\n\nThe vulnerability has been addressed in the latest releases. ZITADEL now explicitly rejects tokens that lack an `iat` claim.\n\n* **4.x**: Upgrade to $\\ge$ [4.15.2](https://github.com/zitadel/zitadel/releases/tag/v4.15.2)\n* **3.x**: Upgrade to $\\ge$ [3.4.12](https://github.com/zitadel/zitadel/releases/tag/v3.4.12)\n\n### Workarounds\n\nThe recommended solution is to update ZITADEL to a patched version.\n\nIf an immediate upgrade is not feasible, ensure at the upstream Identity Provider level that your external IdP explicitly includes the `iat` claim in all signed JWTs.\n\n### Publication Note\n\nThis advisory covers a subset of the security issues originally published on ZITADEL's registry under this tracking ID. To adhere strictly to CVE formatting standards regarding independently fixable flaws, the original \"Token Lifecycle Validation\" disclosure has been split into two granular entries. This entry specifically tracks the missing `iat` claim logic, while a separate companion entry tracks the missing `exp` claim logic: [GHSA-v77h-2w3m-94hx](https://github.com/zitadel/zitadel/security/advisories/GHSA-v77h-2w3m-94hx)\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 [Android-Login-Analysis](https://github.com/Android-Login-Analysis), Jason Zhou and [Pedro Giglioti](https://github.com/Punisher100) for reporting this vulnerability.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/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.20260615122908-fad02c6d9f45"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/zitadel/zitadel/security/advisories/GHSA-wxg7-w2v3-w38g"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-56664"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/zitadel/zitadel/commit/4925fab849d39a88674485d937b79e54318b48a8"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/zitadel/zitadel/commit/d1c3aa84af8fcb0f33910ada30b866f4afb551ac"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/zitadel/zitadel/commit/fad02c6d9f4587956f830d4536c64a9a94baa7ac"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/zitadel/zitadel"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/zitadel/zitadel/releases/tag/v3.4.12"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/zitadel/zitadel/releases/tag/v4.15.2"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-613" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-06-18T13:52:21Z",
    "nvd_published_at" : "2026-07-10T18:16:23Z"
  }
}