CVE-2026-128075: nuxt · Generation of Error Message Containing Sensitive Information
Affects nuxtSource CVE Database V5
Not known to be exploited · CVSS 5.3 Medium : upgrade to 4.6.4 when convenient.
Data as of 13 Nov 2026, 17:49 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 3.1 | 5.3 |
|---|
- Patch
- Available – fixed in 4.6.4
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 to 4.6.4.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| nuxtnuxt | Affected
| Fixed in
|
AI-suggested
Upgrade Nuxt to version 4.6.4 or later, where this issue is fixed. No other mitigation is required as the fix addresses the root cause of sensitive data exposure in error messages.
Description
A vulnerability in Nuxt versions from 3.0.0 up to but not including 4.6.4 causes sensitive information to be exposed in error messages during server rendering. Non-HTTP errors are wrapped and treated as deliberately exposed errors, leading to disclosure of original error messages and data such as upstream fetch URLs, query-string secrets, response bodies, and database hosts. This exposure occurs in the error page payload and JSON error responses, regardless of custom error page rendering. The issue is fixed in version 4.6.4.