Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-56665 medium CVSS 4.2

Vulnerability in github.com/zitadel/zitadel (CVE-2026-56665)

Summary

Vulnerability in github.com/zitadel/zitadel (CVE-2026-56665). Risk of unauthorized operations or information disclosure. Exploitable via exp. Mitigation: upgrade to 3.4.12 or later.

Original description

The description as published by the source.

Summary

A token lifecycle validation vulnerability was discovered in ZITADEL's external JWT Identity Provider (IdP) implementation
Specifically, within the validation pipeline, if an incoming JWT omits the exp claim entirely, the expiration block is silently skipped rather than rejected. The token is treated as valid forever.

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 token lacking an exp claim holds a permanent credential with no automatic expiration or revocation window.

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 exp claim.

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 an external IdP explicitly includes the exp claim in all signed JW…

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-56665 has been found in github.com/zitadel/zitadel.
Attackers can target a specific entry point like exp over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 4.2/10.
What to do: upgrade github.com/zitadel/zitadel to 3.4.12 or later.
If unsure, ask your IT team or search "github.com/zitadel/zitadel CVE-2026-56665" on the vendor's site.

CVE-2026-56665 (github.com/zitadel/zitadel) — CWE-613 / CVSS v3 4.2
Attack vector: remote (network-reachable) / no user interaction
Attack surface: exp
Patched: 3.4.12 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-613) exists in github.com/zitadel/zitadel. Attackers reach the vulnerable code path via exp.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/zitadel/zitadel. Attack surface: exp.

🔥 Severity

Severity: Medium (CVSS 4.2/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 3.4.12.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/zitadel/zitadel' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'github.com/zitadel/zitadel' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で github.com/zitadel/zitadel を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade github.com/zitadel/zitadel to 3.4.12

    ステージング環境で 3.4.12 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

go github.com/zitadel/zitadel
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.4.12"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details