Vulnerability in github.com/zitadel/zitadel (CVE-2026-85057)
Summary
Vulnerability in github.com/zitadel/zitadel (CVE-2026-85057). Confidential information can be exposed externally. Exploitable via org.action.write. Mitigation: upgrade to 1.80.0-v2.20.0.20260717062331-baf6ed501b68 or later.
Original description
The description as published by the source.
Summary
A vulnerability in ZITADEL Actions V1 allows an organization Action author to read files from the ZITADEL host filesystem through the JavaScript require() module loader. On common self-hosted deployments this can be chained to steal bootstrap credentials (including the Login Client PAT) and escalate from a single-tenant organization owner to instance administrator.
Impact
ZITADEL Actions V1 run custom JavaScript inside the ZITADEL server process at OIDC, SAML, and login-flow trigger points. The runtime enables the goja Node-compatible require() registry without restricting the source loader, so Action scripts can load host files readable by the ZITADEL process (notably .js and .json, and in some cases other file contents via error channels).
An attacker with ORG_OWNER on any organization (which includes org.action.write and org.flow.write) can therefore:
- Read process-readable host files, including configuration or secrets mounted into the API container (for example service-account material, projected secrets, or config carrying sensitive values).
- On deployments that follow ZITADEL’s documented bootstrap paths (
ZITADEL_FIRSTINSTANCE_LOGINCLIENTPATPATH,ZITADEL_FIRSTINSTANCE_MACHINEKEYPATH), recover instance-wide credentials such as the IAM_LOGIN_CLIENT PAT or the IAM_OWNER service-account key, enabling escalation to full instance control.
This collapses the expected multi-tenant isolation boundary: a tenant organization adm…
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-85057 has been found in github.com/zitadel/zitadel.
Attackers can target a specific entry point like org.action.write over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 8.7/10.
What to do: upgrade github.com/zitadel/zitadel to 1.80.0-v2.20.0.20260717062331-baf6ed501b68 or later.
If unsure, ask your IT team or search "github.com/zitadel/zitadel CVE-2026-85057" on the vendor's site.
CVE-2026-85057 (github.com/zitadel/zitadel) — CWE-284 / CVSS v3 8.7
Attack vector: remote (network-reachable) / no user interaction
Attack surface: org.action.write / org.flow.write / ZITADEL_FIRSTINSTANCE_LOGINCLIENTPATPATH / ZITADEL_FIRSTINSTANCE_MACHINEKEYPATH
Patched: 1.80.0-v2.20.0.20260717062331-baf6ed501b68 — 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.
A vulnerability (CWE-284) exists in github.com/zitadel/zitadel. Attackers reach the vulnerable code path via org.action.write.
Check the vendor advisory for the affected versions of github.com/zitadel/zitadel. Attack surface: org.action.write / org.flow.write / ZITADEL_FIRSTINSTANCE_LOGINCLIENTPATPATH / ZITADEL_FIRSTINSTANCE_MACHINEKEYPATH.
Severity: High (CVSS 8.7/10). Confidential information can be exposed externally.
Update to 1.80.0-v2.20.0.20260717062331-baf6ed501b68.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
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
-
1Identify 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 し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade github.com/zitadel/zitadel to 1.80.0-v2.20.0.20260717062331-baf6ed501b68ステージング環境で 1.80.0-v2.20.0.20260717062331-baf6ed501b68 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。