Skip to content

← Actionable
High, CVSS 8.7amended

ZITADEL: Actions V1 sandbox escape: host file read via require()

CVE-2026-85057GHSA-fgmf-7rf8-m6vf

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/zitadel/zitadel 1.80.0-v2.20.0.20260717062331-baf6ed501b68), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Affected packages

  • Go github.com/zitadel/zitadel

    Affected
    < 1.80.0-v2.20.0.20260717062331-baf6ed501b68
    Fixed in
    1.80.0-v2.20.0.20260717062331-baf6ed501b68

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
8.7 · CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N
EPSS
  • CVE-2026-85057: 0.39% estimated exploitation activity in the next 30 days; percentile 33.20 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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 ORGOWNER 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…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-fgmf-7rf8-m6vf

  2. Revision 2 · amended ·

    Amended from osv record GO-2026-6591

  3. Revision 1 · created ·

    Published from osv record GHSA-fgmf-7rf8-m6vf

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-85057

Advisory: ZITADEL: Actions V1 sandbox escape: host file read via require()
IDs: CVE-2026-85057, GHSA-fgmf-7rf8-m6vf
Record: https://patchnext.com/advisories/cve-2026-85057 (revision 3, source checked 26 Oct 2026, 15:29 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/zitadel/zitadel 1.80.0-v2.20.0.20260717062331-baf6ed501b68. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/zitadel/zitadel: affected < 1.80.0-v2.20.0.20260717062331-baf6ed501b68; fixed in 1.80.0-v2.20.0.20260717062331-baf6ed501b68

## Suggested inspection (read-only)
- Go github.com/zitadel/zitadel: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/zitadel/zitadel.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GO-2026-6591 (OSV record GO-2026-6591 lists affected ranges: Go github.com/zitadel/zitadel >=0 <1.80.0-v2.20.0.20260717062331-baf6ed501b68 (fixed))
- Verified: https://osv.dev/vulnerability/GHSA-fgmf-7rf8-m6vf (OSV record GHSA-fgmf-7rf8-m6vf lists affected ranges: Go github.com/zitadel/zitadel >=0 <1.80.0-v2.20.0.20260717062331-baf6ed501b68 (fixed))
- Verified: https://github.com/advisories/GHSA-fgmf-7rf8-m6vf (GitHub-reviewed advisory GHSA-fgmf-7rf8-m6vf lists affected ranges: Go github.com/zitadel/zitadel >=0 <1.80.0-v2.20.0.20260717062331-baf6ed501b68)

Commands are suggestions: review each one before running it.

Loading voting…