Nuxt dev server serves files from a parent directory with a lockfile
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- High
- Impact type
- Information disclosure
- Confidentiality · integrity · availability
- High · None · None
- Fix status
- Fixed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA and GitHub. Impact type from CWE-552.
Summary
Nuxt versions from 3.5.0 before 4.6.4 can choose a parent directory as the default workspaceDir when a stray parent lockfile or a parent pnpm or Deno settings file without packages or a workspace is present. When the development server is reachable from an untrusted network, Vite allows /_nuxt/@fs/ requests beneath that widened directory, so unauthenticated clients can read files such as credentials and SSH keys. The issue affects only the development server (CWE-552), and production builds are not affected.
Written with Claude Haiku 5.5 from the sources below · 2026-11-13
Description from the CNA
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.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- No
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
Remediation
Update nuxt to version 4.6.4, and update @nuxt/schema to version 4.6.4, which fixes the issue. The sources list no fixed version for @nuxt/schema other than 4.6.4.
Written with Claude Haiku 5.5 from the sources below · 2026-11-13
- Fix · CNA nuxt (nuxt) Fixed in 4.6.4
- Fix · CNA schema (@nuxt) Fixed in 4.6.4
- Fix · GHSA-mjrq-cffv-q4qc @nuxt/schema (npm) Fixed in 4.6.4 Advisory →
Timeline
- 2026-11-13 Threatist record created from CVE-2026-128070
- 2026-11-13 Alias added: GHSA-mjrq-cffv-q4qc
- 2026-11-13 Fix available: npm/@nuxt/[email protected] · GHSA-mjrq-cffv-q4qc
- 2026-11-13 CVSS score added · GHSA-mjrq-cffv-q4qc
- 2026-11-13 Weakness changed · GHSA-mjrq-cffv-q4qc
- 2026-11-13 4 new references · GHSA-mjrq-cffv-q4qc
- 2026-11-13 CISA SSVC decision points changed
References
More nuxt vulnerabilities
- TI-2023-03020 Code Injection in nuxt/nuxt CVSS 3.1CRITICAL 9.8
- TI-2024-28339 Server-Side Request Forgery (SSRF) in nuxt-icon CVSS 3.1HIGH 8.6
- TI-2024-22685 Remote code execution via the browser when running the test locally in nuxt CVSS 3.1HIGH 8.8
- TI-2026-86049 Unauthenticated SQLite function DoS in Nuxt Content query API CVSS 3.1HIGH 7.5
- TI-2026-26689 Nuxt OG Image vulnerable to DoS via image generation CVSS 4.0MEDIUM 6.9
- TI-2022-04037 Cross-site Scripting (XSS) - DOM in nuxt/framework CVSS 3.1MEDIUM 6.1
Sources
- CVE-2026-128070 · CVE Program
- CVE-2026-128070 · NVD
- FIRST EPSS
- GHSA-mjrq-cffv-q4qc · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences