ZITADEL has potential SSRF via Actions

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

2.1 · CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N · score source

EPSS

• CVE-2026-27945: 0.26% estimated exploitation activity in the next 30 days; percentile 17.40 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary ZITADEL Action V2 (introduced as early preview in 2.59.0, beta in 3.0.0 and GA in 4.0.0) is a webhook based approach to allow developers act on API request to Zitadel and customize flows such the issue of a token. ZITADEL's Action target URLs can point to local hosts, potentially allowing adversaries to gather internal network information and connect to internal services. Impact When the URL points to a local host / IP address, an adversary might gather information about the internal network structure, the services exposed on internal hosts etc. This is sometimes called a Server-Side Request Forgery (SSRF). ZITADEL Actions expect responses according to specific schemas, which reduces the threat vector. Affected Versions Systems running one of the following versions are affected: - 4.x: 4.0.0 through 4.11.0 (including RC version) - 3.x: 3.0.0 to 3.4.6 (including RC versions) - 2.x: 2.59.0 to 2.71.19 Patches The vulnerability has been addressed in the latest releases. The patch…

Published by the source

27 Feb 2026, 21:33 UTC

Last modified by the source

27 Feb 2026, 21:33 UTC

Source last checked

26 Oct 2026, 15:14 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-7777-fhq9-592v

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

# Patch Next advisory brief: CVE-2026-27945

Advisory: ZITADEL has potential SSRF via Actions
IDs: CVE-2026-27945, GHSA-7777-fhq9-592v
Record: https://patchnext.com/advisories/cve-2026-27945 (revision 1, source checked 26 Oct 2026, 15:14 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 2.1)
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/v2 4.11.1, 1.80.0-v2.20.0.20260225053328-b2532e966621. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/zitadel/zitadel/v2: affected >= 2.59.0, < 4.11.1; < 1.80.0-v2.20.0.20260225053328-b2532e966621; fixed in 1.80.0-v2.20.0.20260225053328-b2532e966621, 4.11.1

## Suggested inspection (read-only)
- Go github.com/zitadel/zitadel/v2: 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/v2.
- 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://github.com/advisories/GHSA-7777-fhq9-592v (GitHub-reviewed advisory GHSA-7777-fhq9-592v lists affected ranges: Go github.com/zitadel/zitadel/v2 >=2.59.0 =0 <1.80.0-v2.20.0.20260225053328-b2532e966621)

Commands are suggestions: review each one before running it.