Loading vulnerability…
CVE-2025-67494 is a server-side request forgery vulnerability in ZITADEL, affecting versions 4.7.0 and below. The flaw is in the ZITADEL Login UI (V2), which incorrectly treats the x-zitadel-forward-host header as a trusted fallback host across deployments, including self-hosted environments. Because this header can be influenced by an unauthenticated requester, an attacker can cause the ZITADEL server to issue HTTP requests to arbitrary attacker-chosen destinations, including internal network addresses and services not otherwise reachable externally. The vulnerability is described as a full-read SSRF, meaning the attacker can not only trigger outbound requests but also read the returned responses. This enables access to internal resources and sensitive data through the vulnerable server as a proxy. The issue is fixed in ZITADEL 4.7.1.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository contains a fully automated exploit for CVE-2025-67494, a critical unauthenticated SSRF vulnerability in ZITADEL (versions v4.0.0-rc.1 through 4.7.0). The exploit is implemented in Python (exploit.py) and is designed to: 1. Spin up a vulnerable ZITADEL environment using Docker Compose (docker-compose.yml). 2. Create a webhook.site endpoint to capture out-of-band (OOB) SSRF requests. 3. Exploit the SSRF by sending a request to the ZITADEL Login UI with a crafted x-zitadel-forward-host header, causing the server to make a request to the attacker's webhook. 4. Retrieve the leaked Bearer token from the webhook.site logs. 5. Use the stolen token to enumerate sensitive information from the ZITADEL Management API, including IAM, organization, user, project, and domain data. The exploit is operational and automates the entire attack chain, requiring only the target UI URL (and optionally the API URL). It leverages several network endpoints, including the ZITADEL Login UI, webhook.site, and the ZITADEL Management API. The repository is structured with a single main exploit script (exploit.py), supporting configuration files for Python dependencies (pyproject.toml), and a Docker Compose file to facilitate local testing. The README.md provides detailed usage instructions, output examples, and a technical breakdown of the vulnerability and exploit process.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
6 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A critical vulnerability in ZITADEL (CVSS 9.3) described as enabling SSRF leading to internal breach and account hijack via XSS.
An unauthenticated, full-read Server-Side Request Forgery (SSRF) in ZITADEL Login UI (V2) caused by trusting the x-zitadel-forward-host header, enabling arbitrary outbound HTTP requests (including to internal addresses) and reading responses for data exfiltration and network segmentation bypass.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.