Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-72744 medium CVSS 6.2

Information Disclosure in nuxt (CVE-2026-72744)

Summary

Vulnerability in nuxt (CVE-2026-72744). Confidential information can be exposed externally. Exploitable via GET /.well-known/appspecific/com.chrome.devtools.json. Mitigation: upgrade to 3.21.10 or later.

Original description

The description as published by the source.

Impact

When a Nuxt dev server is bound to a network-reachable interface (for example nuxt dev --host for on-device testing), the default-enabled Chrome DevTools workspace endpoint GET /.well-known/appspecific/com.chrome.devtools.json returns the absolute project root (workspace.root, i.e. rootDir) and a persistent per-project workspace UUID.

GHSA-rq7w-g337-39qq added a gate (isLocalDevRequest) intended to restrict this endpoint to local requests, but that gate is header-based: it trusts request metadata rather than the connected peer address. A request with no Sec-Fetch-Site, Origin, and Referer headers (normal for a non-browser client such as curl) is treated as local, and the Host allow-list is compared against the attacker-supplied Host header. As a result, any unauthenticated host that can reach the dev server on the LAN can retrieve the project's absolute filesystem path and workspace UUID, for example with curl -H 'Host: localhost' http://:3000/.well-known/appspecific/com.chrome.devtools.json.

This is information disclosure only: there is no file read, file write, or code execution reachable from the endpoint. It requires the dev server to be reachable beyond loopback and experimental.chromeDevtoolsProjectSettings to be enabled (it defaults to true). Production builds are unaffected, because the endpoint is registered only as a development handler.

Patches

Fixed in nuxt@4.5.1 and nuxt@3.21.10. The endpoint now additionally…

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-72744 has been found in nuxt.
Attackers can target a specific entry point like GET /.well-known/appspecific/com.chrome.devtools.json over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 6.2/10.
What to do: upgrade nuxt to 3.21.10 or later.
If unsure, ask your IT team or search "nuxt CVE-2026-72744" on the vendor's site.

CVE-2026-72744 (nuxt) — CWE-200 / CVSS v3 6.2
Attack vector: local / unauthenticated / no user interaction
Attack surface: GET /.well-known/appspecific/com.chrome.devtools.json / workspace.root / rootDir / isLocalDevRequest
Patched: 3.21.10 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

Information disclosure (CWE-200) exists in nuxt. Attackers reach the vulnerable code path via GET /.well-known/appspecific/com.chrome.devtools.json without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of nuxt. Attack surface: GET /.well-known/appspecific/com.chrome.devtools.json / workspace.root / rootDir / isLocalDevRequest.

🔥 Severity

Severity: Medium (CVSS 6.2/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 3.21.10.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual GET /.well-known/appspecific/com.chrome.devtools.json requests with malformed payloads or SQL meta-characters. Run grep -r 'nuxt' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'nuxt' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で nuxt を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Hunt for indicators of compromise detect 
    grep 'GET /.well-known/appspecific/com.chrome.devtools.json' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

    アクセスログで GET /.well-known/appspecific/com.chrome.devtools.json への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。

  3. 3
    Apply patch patch 
    Upgrade nuxt to 3.21.10

    ステージング環境で 3.21.10 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。

  4. 4
    Post-deployment verification verify 
    Replay attack against GET /.well-known/appspecific/com.chrome.devtools.json on staging to confirm patch closes the vector

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

npm nuxt
[{"type":"SEMVER","events":[{"introduced":"3.21.7"},{"fixed":"3.21.10"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details