cve.bz

CVE-2026-85057 zitadel zitadel: Improper Access Control

8.7 highEPSS 0.4%Fix available

High (8.7) in zitadel zitadel. EPSS 0.4% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/zitadel/zitadel 1.80.0-v2.20.0.20260717062331-baf6ed501b68.

On this page
ZITADEL is an open source identity management platform. From 3.0.0 until 3.4.13 and 4.16.1, ZITADEL Actions V1 enables the goja Node-compatible require() registry without restricting its filesystem source loader. An organization Action author with ORG_OWNER, org.action.write, and org.flow.write permissions can run JavaScript at OIDC, SAML, and login-flow trigger points and load files readable by the ZITADEL server process. This can disclose mounted configuration and secrets, including credentials stored through ZITADEL_FIRSTINSTANCE_LOGINCLIENTPATPATH or ZITADEL_FIRSTINSTANCE_MACHINEKEYPATH, and recovered bootstrap credentials can enable escalation from an organization administrator to an instance administrator. The issue affects Actions V1, and host command execution is not established. This issue is fixed in versions 3.4.13 and 4.16.1.

Severity

CVSS 3.1

8.7 high
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N
EPSS
0.4% (unchanged from 0.4% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 34th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-10-05. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-284 Improper Access Control
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

  • github.com/zitadel/zitadel (Go): fixed in 1.80.0-v2.20.0.20260717062331-baf6ed501b68

Ask an AI about this CVE

Show the promptExplain CVE-2026-85057 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-85057?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-85057?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-85057 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
zitadel>= 3.0.0, < 3.4.13
zitadel>= 4.0.0, < 4.16.1

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-fgmf-7rf8-m6vfGogithub.com/zitadel/zitadel<1.80.0-v2.20.0.20260717062331-baf6ed501b681.80.0-v2.20.0.20260717062331-baf6ed501b68
GO-2026-6591Gogithub.com/zitadel/zitadel<1.80.0-v2.20.0.20260717062331-baf6ed501b681.80.0-v2.20.0.20260717062331-baf6ed501b68

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-284 (17).

References

Check your stackJSON