# CVE-2026-128070: Nuxt dev server serves files from a parent directory that contains a lockfile


- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 13 Nov 2026
- **Updated:** 13 Nov 2026
- **Also known as:** DHI-qbl4-mlp2-dv7o-qivv, GHSA-mjrq-cffv-q4qc

## What is CVE-2026-128070?

CVE-2026-128070 is a medium-severity vulnerability in @nuxt nuxt, published on 13 Nov 2026. 

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

Weakness: CWE-552 (Files or Directories Accessible to External Parties)

## Which versions are affected by CVE-2026-128070?

1 open source package ship an affected version, including @nuxt/schema.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `@nuxt/schema` | npm | `pkg:npm/%40nuxt/schema` | From 3.5.0 | 4.6.4 |

Status by vendor (upstream, then each distribution release and vendor build):

| Who | Release | Status | Packages | Fixed in |
| --- | --- | --- | --- | --- |
| Upstream |  | fixed | `@nuxt/schema` | 4.6.4 |

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

Upgrade @nuxt/schema to 4.6.4 or later.

## Is CVE-2026-128070 being exploited?

There is no known exploitation of CVE-2026-128070 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-128070 and fix it if it is affected.

What it is: CVE-2026-128070 is a medium-severity vulnerability in @nuxt nuxt, published on 13 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-128070 in the wild and no public exploit code.

Affected packages and fixed versions:
- @nuxt/schema (npm): affected from 3.5.0; fixed in 4.6.4

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-128070/ (Markdown: https://insights.sbomify.com/CVE-2026-128070/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-128070
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-128070
- OSV: https://osv.dev/vulnerability/CVE-2026-128070

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-128070/
Summaries are generated and may contain mistakes; the official description above is the record.
