LiveActive security incident?Get immediate response
CVE Record

CVE-2026-27945: ZITADEL has potential SSRF via Actions

ZITADEL is an open source identity management platform. 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. 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. The patch in version 4.11.1 resolves the issue by checking the target URL against a denylist. By default localhost, resp. loopback IPs are denied. Note that this fix was only released on v4.x. Due to the stage (preview / beta) in which the functionality was in v2.x and v3.x, the changes that have been applied to it since then and the severity, respectively the actual thread vector, a backport to the corresponding versions was not feasible. Please check the workaround section for alternative solutions if an upgrade to v4.x is not possible. If an upgrade is not possible, prevent actions from using unintended endpoints by setting network policies or firewall rules in one's own infrastructure. Note that this is outside of the functionality provided by Zitadel.

LowCVSS 2.1Not KEV-listedUpdated
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

ZITADEL Actions can be configured to call localhost or internal IP addresses, creating a limited server-side request forgery risk. An attacker with high privileges could use this to learn about internal services. The vendor rates this low severity, and no active exploitation is cited in the provided sources.

Executive priority

Treat as a controlled, low-severity remediation item unless ZITADEL Actions are widely delegated or deployed in sensitive networks. Prioritize upgrade or egress controls during the next maintenance window, and verify no Actions target internal services unexpectedly.

Technical view

CVE-2026-27945 affects ZITADEL Action V2 in versions >=2.59.0 and <4.11.1. Action target URLs may reach local hosts or internal services. Required privileges are high, responses must match expected schemas, and impact is limited to low confidentiality and integrity effects. Version 4.11.1 adds URL denylist checks blocking localhost and loopback by default.

Likely exposure

Exposure is most relevant for self-hosted ZITADEL deployments using Action V2 with administrators or developers able to configure action target URLs. Versions 2.59.0 through 3.x are affected, but the feature was preview or beta there. ZITADEL 4.x before 4.11.1 is also affected.

Exploitation context

The sources describe potential SSRF but do not cite public exploitation or KEV listing. Abuse requires high privileges and valid Action configuration access. The response schema requirement reduces usefulness, but internal network probing or interaction with unintended endpoints may still be possible.

Researcher notes

The advisory states no backport was feasible for v2.x and v3.x because the feature was preview or beta and later changed. The provided release references include v3.4.7 and v4.11.0, while the described fix is 4.11.1; validate exact fixed release through the GitHub advisory before closure.

Mitigation direction

  • Upgrade ZITADEL 4.x deployments to version 4.11.1 or later when available.
  • If unable to upgrade, restrict Action egress with network policies or firewall rules.
  • Review vendor advisory guidance for v2.x and v3.x deployments.
  • Limit who can configure ZITADEL Actions and audit recent Action target URL changes.

Validation and detection

  • Inventory ZITADEL versions and identify deployments between 2.59.0 and 4.11.1.
  • Determine whether Action V2 is enabled or used in each deployment.
  • Review configured Action target URLs for localhost, loopback, or internal-only destinations.
  • Confirm egress controls block unintended internal endpoints from the ZITADEL runtime.
  • Verify upgraded 4.x instances enforce the vendor denylist behavior.
Prepared
Confidence
high
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-918: Information exposure and cloud metadata lookup

Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
description · low confidence lookup

Cloud metadata behavior lookup

The CVE wording references SSRF or metadata access, so cloud discovery and credential material review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-27945 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Low
CVSS
2.1 (4.0)
Known Exploited
No
Published

Vector: 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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
2.1CVSS 4.0LowCVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N——Primary CVE score

Vulnerability scoring details

Base CVSS 4.0 score

2.1Low
CVSS 4.0 vector shape for CVE-2026-27945Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: 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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
zitadelzitadel>= 2.59.0, < 4.11.1Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-918 · source CWE mapping

Server-Side Request Forgery (SSRF)

Server-Side Request Forgery (SSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.