ZDF
Sign inSign up

Vulnerabilities

Security fix · GHSA-7c4v-fwgw-9rf7

Nuxt dev server discloses project root and workspace UUID via the Chrome DevTools workspace endpoint

Published Jul 27, 2026 · catalog updated Jul 27, 2026 · Nuxt dev server discloses

Last checked Nov 2, 2026. A connected source was read within the last 7 days.

Open the advisory

Exploitation likelihood is not on this record for GHSA-7c4v-fwgw-9rf7. A missing EPSS score is not a low risk. Compare Nuxt dev server discloses with the linked advisory before you change production.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (Nuxt dev server discloses).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
  • EPSS is missing. A missing score is not a low risk.
Severity
Low—
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
Awaiting synchronization with FIRST
Remediation
Version ranges on file
Affected products
npm nuxt

### Impact When a Nuxt dev server is bound to a network-reachable interface (for example for on-device testing), the default-enabled Chrome DevTools workspace endpoint returns the absolute project root ( , i.e. ) and a persistent per-project workspace UUID. added a gate ( ) 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 , , and headers (normal for a non-browser client such as ) is treated as local, and the allow-list is compared against the attacker-supplied 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 . 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 to be enabled (it defaults to ). Production builds are unaffected, because the endpoint is registered only as a development handler. ### Patches Fixed in and . The endpoint now additionally requires the connected TCP peer to be a loopback address, verified from the socket rather than from request headers, so a non-loopback LAN client is rejected regardless of the , , , or headers it sends. The shared header-based check is left unchanged, so the CSRF / same-origin behaviour that other dev handlers rely on is preserved. After this fix, Chrome DevTools workspace auto-mapping only works when the browser reaches the dev server over loopback ( / / ), which matches the feature's intent (the browser and dev server sharing a filesystem). ### Workarounds - Do not bind the dev server to a non-loopback interface on an untrusted network, or restrict access to the dev port with a firewall. - Disable the feature by setting in . ### References - Original disclosure for the same endpoint (incompletely fixed): GHSA-rq7w-g337-39qq - Related dev-server same-

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • npm nuxt>= 3.21.7, < 3.21.10
  • npm nuxt>= 4.4.7, < 4.5.1

How to fix GHSA-7c4v-fwgw-9rf7

  • Upgrade

    GHSA-7c4v-fwgw-9rf7 lists a fix boundary at 3.21.10. Compare the installed build with that boundary before you change production.

  • Version check

    Affected < 3.21.10

  • Advisory

    Open the inventory_github record and follow its fix.

  • Official advisories

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

Exploitation likelihood is not on this record for GHSA-7c4v-fwgw-9rf7. A missing EPSS score is not a low risk. Compare Nuxt dev server discloses with the linked advisory before you change production.

Which versions are affected?

Compare what you have installed with >= 3.21.7, < 3.21.10, >= 4.4.7, < 4.5.1. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-200: Exposure of Sensitive Information. EPSS is not on this record yet. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Technology hubs

Nuxt security

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Jul 27, 2026 · Maintainer security tabs

    Detected

    ### Impact When a Nuxt dev server is bound to a network-reachable interface (for example for on-device testing), the default-enabled Chrome DevTools workspace endpoint returns the absolute project root ( , i.e. ) and a persistent per-project workspace UUID. added a gate ( ) intended to restrict this endpoint to local requests, but that gate is header-based: it trusts request metadata rather than t

Sources

  • Maintainer security tabsVendor advisoryGHSA-7c4v-fwgw-9rf7

    ### Impact When a Nuxt dev server is bound to a network-reachable interface (for example for on-device testing), the default-enabled Chrome DevTools workspace endpoint returns the absolute project root ( , i.e. ) and a persistent per-project workspace UUID. added a gate ( ) intended to restrict this endpoint to local requests, but that gate is header-based: it trusts request metadata rather than t

    github.com

Freshness

Last verified in this catalog Jul 27, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • Maintainer security tabsNov 2, 2026