Public vulnerability disclosure

CVE-2026-128070

Nuxt dev server serves files from a parent directory that contains a lockfile

publishedCWE-552

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.

Technical severity5.9 mediumCVSS 3.1 · CNA: GitHub_M
Published2026-11-13Source updated 2026-11-13
Collected2026-11-132 attributed sources

Fixes and workarounds

Fix

@nuxt/schema (npm): OSV reports a fixed version 4.6.4. Check the advisory for supported release branches.

Source: OSV GHSA-mjrq-cffv-q4qc

Affected products and versions

Affected products, source version ranges and reporting authorities
ProductVersionsAuthority
nuxt
nuxt
>= 3.5.0, < 4.6.4 (affected) CNA: GitHub_M
schema
@nuxt
>= 3.5.0, < 4.6.4 (affected) CNA: GitHub_M
@nuxt/schema

@nuxt/schema
npm
≥ 3.5.0; < 4.6.4 (affected, semver); OSV events: introduced 3.5.0; fixed 4.6.4
Source events (semver)
[
  {
    "introduced": "3.5.0"
  },
  {
    "fixed": "4.6.4"
  }
]

Other versions: unaffected
OSV GHSA-mjrq-cffv-q4qc

Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.

CVSS assessments

CVSS scores, vectors and reporting authorities
Version / scoreVectorAuthority
3.1 / 5.9
medium
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:NCNA: GitHub_M

Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

References

For agents and automation

Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.

Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.

Endpoints and access details

https://api.y2.dev/api/v2/cyber/cves
https://api.y2.dev/api/v2/cyber/cves/{cveId}

A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.

For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.

Agent access JSON · OpenAPI · CVE API guide