CVE
Nuxt file disclosure in dev server via parent directory
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
- Exploited
- No known exploitation
- Fix
- Fixed in 4.6.4
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 4.6.4.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.41% · 36th percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 39/100 · provisional
- The share of the registry's downloads of each affected package in the window that were versions inside the affected ranges. Downloads, not users or installs: CI runs and mirrors inflate the counts.
- 83% of @nuxt/schema downloads last week were affected versions (3.5M).npm, 4.2M downloads in the last 7 days, read Nov 14, 2026
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
Nuxt's development server can serve files from a parent directory that holds a stray lockfile or a pnpm or Deno settings file without a workspace declaration, which affects the nuxt and @nuxt/schema packages. If the dev server is reachable from an untrusted network, an unauthenticated remote attacker can read sensitive files such as credentials and SSH keys; production builds are not affected.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Original description
Nuxt is an open-source web development framework for Vue.js. From 3.5.0 until 4.6.4, Nuxt can choose a parent directory as the default workspaceDir in either of two cases: a stray parent lockfile when the project is outside a Git repository and has no workspace file above it, or a parent pnpm or Deno settings file that does not declare packages or a workspace, including when the project is inside a Git repository. When the development server is reachable from an untrusted network, Vite permits /_nuxt/@fs/ requests beneath that widened directory, allowing unauthenticated clients to read files such as credentials and SSH keys. The issue affects the development server only; production builds and projects whose parent directories contain no qualifying files are unaffected. This issue is fixed in version 4.6.4.
cve.now Index
- Exploitation0/40No signal
- Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Unknown: No advisory context yet
- Reach16/20@nuxt/schema: 4.2M downloads a week
- Severity5.9/10CVSS 5.9
- No patch0/5No signal
What would change the score
- Would score about 84 if added to CISA KEV
- Would score about 79 if CISA's SSVC rates exploitation active
- Would score about 44 if advisories confirm default setups are exposed
Impact
What to do
Upgrade to a fixed version: 4.6.4.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-128070 (Nuxt dev server serves files from a parent directory that contains a lockfile), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-128070 (entry last updated 2026-11-13):
Affected:
- nuxt nuxt: from 3.5.0, fixed in 4.6.4
- @nuxt schema: from 3.5.0, fixed in 4.6.4
- npm package @nuxt/schema: from 3.5.0, fixed in 4.6.4
Fixed versions: 4.6.4.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-128070 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-128070 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Packages (npm): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/nuxt/nuxt/security/advisories/GHSA-mjrq-cffv-q4qc
- https://github.com/nuxt/nuxt/commit/89d3306d1976dd52ac2e73078806a3e889cbb8bd
- https://github.com/nuxt/nuxt/releases/tag/v4.6.4
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-128070
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-128070"}.Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- nuxt nuxt
From 3.5.0 · fixed in 4.6.4
- @nuxt schema
From 3.5.0 · fixed in 4.6.4
- @nuxt/schemanpm
From 3.5.0 · fixed in 4.6.4
Fixed in 4.6.4 (released Nov 2, 2026, 11 days before disclosure).
The latest release, 4.6.4, is not affected.
Evidence 5
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 2
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-128070
Is CVE-2026-128070 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-128070?
nuxt: from 3.5.0 before 4.6.4. schema: from 3.5.0 before 4.6.4. @nuxt/schema (npm): from 3.5.0 before 4.6.4.Source: cve.now feed data
How do I fix CVE-2026-128070?
Upgrade to a fixed version: 4.6.4.Source: cve.now feed data