CVE-2026-128070: nuxt · Exposed Files or Directories
Affects nuxtSource CVE Database V5
Not known to be exploited · CVSS 5.9 Medium : upgrade to 4.6.4 when convenient.
Data as of 13 Nov 2026, 17:36 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 3.1 | 5.9 |
|---|
- Patch
- Available – fixed in 4.6.4
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 13 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.
What to do
Upgrade nuxt and schema to 4.6.4.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| nuxtnuxt | Affected
| Fixed in
|
| @nuxtschema | Affected
| Fixed in
|
AI-suggested
Upgrade Nuxt to version 4.6.4 or later, where this issue is fixed. Avoid exposing the development server to untrusted networks. Since the vulnerability affects only the development server, production builds are not impacted.
Description
A vulnerability in Nuxt versions from 3.5.0 up to but not including 4.6.4 allows unauthenticated clients to read arbitrary files from parent directories via the development server. This occurs when the development server is accessible from an untrusted network and certain parent lockfiles or settings files cause Nuxt to select a parent directory as the workspace directory. The issue affects only the development server and not production builds. It is fixed in version 4.6.4.