Nuxt sensitive data exposure in server-rendering errors
nuxt
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| nuxt npm |
|
|
Original description
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.
From the CVE record · GitHub_M
References
- github.com/nuxt/nuxt/security/advisories/GHSA-96x6-fvhx-49hg
- github.com/nuxt/nuxt/commit/8c56b71e4d0377c5c047799078db09c6b3d4fde5
- github.com/nuxt/nuxt/releases/tag/v4.6.4
- github.com/CVEProject/cvelistV5/tree/main/cves/2026/128xxx/CVE-2026-128075.json
- nvd.nist.gov/vuln/detail/CVE-2026-128075
- github.com/nuxt/nuxt