Skip to content
KitploitKITPLOIT
ToolsBlog
Submit
ToolsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

··Feeds·Contact·Privacy·© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
CVE-2026-72744-poc — Proof-of-concept exploit for CVE-2026-72744, an information disclosure vulnerability in Nuxt dev server's Chrome DevTools workspace endpoint. Demonstrates the flaw and verifies the fix. | Kitploit
Tools/GitHubGitHub/saku0512/cve-2026-72744-poc
Vulnerability AnalysisExploitationWeb Application ExploitationPapers & ResearchLearning & Education
GitHubsaku0512/cve-2026-72744-poc

CVE-2026-72744-poc

Proof-of-concept exploit for CVE-2026-72744, an information disclosure vulnerability in Nuxt dev server's Chrome DevTools workspace endpoint. Demonstrates the flaw and verifies the fix.

View Repository
5h 18m agoNot yet reviewed

Most Popular

View all →

Discover the most used tools by our community.

Explore all tools

Browse our collection of tools

View all tools →
Share

CVE-2026-72744: Nuxt Chrome DevTools endpoint information disclosure PoC

Japanese version

Overview

This repository reproduces CVE-2026-72744, an information disclosure in Nuxt's development-only Chrome DevTools workspace endpoint.

The vulnerable server uses attacker-controlled HTTP headers, including Host, to decide whether a request is local. When the development server is bound to a network-reachable interface, an unauthenticated client can send Host: localhost and retrieve the absolute project root and persistent workspace UUID.

The Docker environment runs Nuxt 4.5.0 (vulnerable) and 4.5.1 (fixed) side by side. The PoC does not read or write arbitrary files and does not execute code.

Affected versions

  • Nuxt >= 4.4.7, < 4.5.1
  • Nuxt >= 3.21.7, < 3.21.10
  • Fixed in 4.5.1 and 3.21.10
  • Development servers only; production builds are unaffected

The Chrome DevTools project settings feature must be enabled (the default), and the development server must be reachable beyond loopback.

Usage

root@kitploit:~
docker compose up -d --build

python3 exploit.py -t http://localhost:3000 --expect vulnerable
python3 exploit.py -t http://localhost:3001 --expect fixed

Expected results:

  • port 3000 / Nuxt 4.5.0: HTTP 200 with workspace.root and workspace.uuid
  • port 3001 / Nuxt 4.5.1: HTTP 403

Manual requests:

root@kitploit:~
curl -i -H 'Host: localhost' \
  http://localhost:3000/.well-known/appspecific/com.chrome.devtools.json

curl -i -H 'Host: localhost' \
  http://localhost:3001/.well-known/appspecific/com.chrome.devtools.json

Docker port forwarding makes the host-side request appear as a non-loopback peer inside the container, reproducing the relevant LAN-request condition on a single machine.

Cleanup:

root@kitploit:~
docker compose down -v

Mitigation

Upgrade to Nuxt 4.5.1 / 3.21.10 or later. As a workaround, bind the development server only to loopback or set experimental.chromeDevtoolsProjectSettings: false.

References

  • GitHub Security Advisory GHSA-7c4v-fwgw-9rf7
  • Nuxt 4.5.1 release
  • Fix commit
  • NVD: CVE-2026-72744

Use only in environments you own or are explicitly authorized to test.

Download Tool