Loading vulnerability…
CVE-2026-72744 is an information-disclosure vulnerability in Nuxt development servers in versions 4.4.7 through 4.5.0 and 3.21.7 through 3.21.9. The Chrome DevTools workspace settings handler uses the header-derived Host value in its local-request validation rather than validating the connected peer address. A remote requester can spoof the Host header to bypass this check and obtain Chrome DevTools workspace metadata. Production builds are not affected.
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 eight-file repository is a self-contained, non-destructive Python proof of concept for CVE-2026-72744, an information disclosure affecting Nuxt development servers. The primary entry point, exploit.py, accepts a configurable base URL, sends a request to the Chrome DevTools workspace endpoint with a spoofed Host header (localhost), parses the JSON response, and reports a target as vulnerable only when workspace.root and workspace.uuid are disclosed. It also supports fixed-version validation by expecting HTTP 403. The repository includes a minimal Vue application and Nuxt configuration, plus Docker/Docker Compose files that build Nuxt 4.5.0 on host port 3000 and Nuxt 4.5.1 on port 3001 for vulnerable-versus-fixed testing. No command execution, arbitrary file read/write, persistence, or destructive behavior is implemented.
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.
1 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.