Categories
CVE-2026-55669 medium CVSS 4.2

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

Summary

Vulnerability in github.com/zitadel/zitadel (CVE-2026-55669). Risk of unauthorized operations or information disclosure. Exploitable via iss. Mitigation: upgrade to 1.80.0-v2.20.0.20260615132747-d184e976fc79 or later.

Original description

The description as published by the source.

ZITADEL is an open source identity management platform. Prior to 3.4.12 and 4.15.2, ZITADEL's external JWT Identity Provider validates a token's signature and issuer (iss) but not the audience (aud) claim, allowing a validly signed token from a trusted issuer for another relying party to be accepted by ZITADEL. This issue is fixed in versions 3.4.12 and 4.15.2.

Source: GitHub Security Advisories (Global) 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-55669 has been found in github.com/zitadel/zitadel.
Attackers can target a specific entry point like iss 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 1.80.0-v2.20.0.20260615132747-d184e976fc79 or later.
If unsure, ask your IT team or search "github.com/zitadel/zitadel CVE-2026-55669" on the vendor's site.

CVE-2026-55669 (github.com/zitadel/zitadel) — CWE-346 / CVSS v3 4.2
Attack vector: remote (network-reachable) / no user interaction
Attack surface: iss / aud
Patched: 1.80.0-v2.20.0.20260615132747-d184e976fc79 — 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-346) exists in github.com/zitadel/zitadel. Attackers reach the vulnerable code path via iss.

📍 Affected scope

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

🔥 Severity

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

🔧 How to fix

Update to 1.80.0-v2.20.0.20260615132747-d184e976fc79.

🛡️ 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 1.80.0-v2.20.0.20260615132747-d184e976fc79

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

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

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

Affected packages

go github.com/zitadel/zitadel
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"1.80.0-v2.20.0.20260615132747-d184e976fc79"}]}]

References

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