CVSS 3.1
5.9 mediumCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:NCVE-2026-128070 Nuxt dev server serves files from a parent directory that contains a lockfile
Medium (5.9). Fixed in @nuxt/schema 4.6.4.
On this page
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.
Severity
- CISA's assessment (SSVC)
- Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-11-13. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
- CWE
- CWE-552 Files or Directories Accessible to External Parties
- OWASP Top 10
- A01:2025 Broken Access Control
- Published
- Modified
- Assigned by
- GitHub_M (CNA)
- NVD analysis
- Awaiting analysis
- Record from
- the NVD, synced
Ask an AI about this CVE
Show the prompt
Explain CVE-2026-128070 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-128070?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-128070?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-128070 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Badge for a README or a site
An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:
[](https://cve.bz/cve/CVE-2026-128070)
HTML:
<a href="https://cve.bz/cve/CVE-2026-128070"><img src="https://cve.bz/cve/badge/CVE-2026-128070.svg" alt="CVE-2026-128070"></a>
Affected
- @nuxt:schema
- nuxt:nuxt
Versions
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| nuxt | >= 3.5.0, < 4.6.4 |
| @nuxt schema | >= 3.5.0, < 4.6.4 |
Fix and patched versions
@nuxt/schema(npm): fixed in 4.6.4
Packages (OSV)
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-mjrq-cffv-q4qc | npm | @nuxt/schema | >=3.5.0 <4.6.4 | 4.6.4 |
Attack patterns (CAPEC)
- CAPEC-150 Collect Data from Common Resource Locations Severity: Medium
- CAPEC-639 Probe System Files Severity: Medium
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.