Nuxt exposes error details from unhandled server rendering errors
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Information disclosure
- Confidentiality · integrity · availability
- Low · None · None
- Fix status
- Fixed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA and GitHub. Impact type from CWE-209.
Summary
Nuxt from 3.0.0 before 4.6.4 wraps non-HTTP server rendering errors in createError, so production responses expose their original message and data. The error page payload and JSON error response can reveal details such as upstream URLs, query-string secrets, or database hosts, even with a custom error.vue. An unauthenticated remote attacker can read this data without user interaction (CWE-209).
Written with Claude Haiku 5.5 from the sources below · 2026-11-16
Description from the CNA
Nuxt is an open-source web development framework for Vue.js. From 3.0.0 until 4.6.4, Nuxt wraps non-HTTP errors thrown during server rendering with createError and incorrectly treats the result as an error deliberately exposed by the application. In production, the error page payload (__NUXT_DATA__) and JSON error response can therefore disclose the original message and data, including an upstream $fetch URL, query-string secrets, response bodies, database hosts, or similar sensitive details, regardless of what a custom error.vue renders. Errors deliberately created with createError or showError, errors returned by useFetch or useAsyncData, and server/api routes are not affected because their client-visible behavior is intentional or follows a different path. This issue is fixed in version 4.6.4.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- Yes
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| nuxt | nuxt | 3.0.0 to before 4.6.4 | 4.6.4 | Patch available | CNA |
| — | nuxt (npm) | 4.0.0 to before 4.6.4 | 4.6.4 | Patch available | GHSA-96x6-fvhx-49hg |
| — | nuxt (npm) | 3.0.0 and later | — | No fix listed | GHSA-96x6-fvhx-49hg |
- nuxt Vendornuxt Affected 3.0.0 to before 4.6.4 Fixed in 4.6.4 Patch available CNA
- nuxt (npm) Vendor— Affected 4.0.0 to before 4.6.4 Fixed in 4.6.4 Patch available GHSA-96x6-fvhx-49hg
- nuxt (npm) Vendor— Affected 3.0.0 and later Fixed in — No fix listed GHSA-96x6-fvhx-49hg
Remediation
Upgrade nuxt to version 4.6.4, which fixes this flaw. The sources list no fixed version for nuxt.
Written with Claude Haiku 5.5 from the sources below · 2026-11-16
- Fix · CNA nuxt (nuxt) Fixed in 4.6.4
- Fix · GHSA-96x6-fvhx-49hg nuxt (npm) Fixed in 4.6.4 Advisory →
Timeline
- 2026-11-13 Threatist record created from CVE-2026-128075
- 2026-11-13 CISA SSVC decision points changed
- 2026-11-16 Alias added: GHSA-96x6-fvhx-49hg
- 2026-11-16 Fix available: npm/[email protected] · GHSA-96x6-fvhx-49hg
- 2026-11-16 CVSS score added · GHSA-96x6-fvhx-49hg
- 2026-11-16 Weakness changed · GHSA-96x6-fvhx-49hg
- 2026-11-16 5 new references · GHSA-96x6-fvhx-49hg
References
More nuxt vulnerabilities
- TI-2023-03020 Code Injection in nuxt/nuxt CVSS 3.1CRITICAL 9.8
- TI-2024-28339 Server-Side Request Forgery (SSRF) in nuxt-icon CVSS 3.1HIGH 8.6
- TI-2024-22685 Remote code execution via the browser when running the test locally in nuxt CVSS 3.1HIGH 8.8
- TI-2026-86049 Unauthenticated SQLite function DoS in Nuxt Content query API CVSS 3.1HIGH 7.5
- TI-2026-26689 Nuxt OG Image vulnerable to DoS via image generation CVSS 4.0MEDIUM 6.9
- TI-2022-04037 Cross-site Scripting (XSS) - DOM in nuxt/framework CVSS 3.1MEDIUM 6.1
Sources
- CVE-2026-128075 · CVE Program
- CVE-2026-128075 · NVD
- FIRST EPSS
- GHSA-96x6-fvhx-49hg · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences