- Severity: MEDIUM
- CVE: CVE-2026-128075
- Ecosystems: npm, npm
- Packages: nuxt, nuxt
### Summary
When a page, plugin or route middleware throws an error that is not an HTTP error, Nuxt wraps it with `createError` before rendering the error page. The wrapped error was treated as one the app raised deliberately, so in production its `message` and `data` were sent to the client in the error page payload (`__NUXT_DATA__`) and in JSON error responses. For a failed `$fetch`, that is the URL that was requested (including its query string) and the body of the upstream error response.
### Impact
An application is affected if server-rendered code lets an error with sensitive details reach the error page, for example:
“`vue
“`
Anyone who can make the request fail (for example by requesting an id the upstream service rejects) receives `[GET] “http://users.internal/users/1?token=…”: 502` and the upstream response body. This happens regardless of what a custom `error.vue` renders, because the details are part of the payload. With the default configuration, the HTTP status line is not affected.
The same applies to any other error thrown during server rendering, such as a database driver error whose message names an internal host.
Errors created deliberately with `createError` (or `showError`) are not affected: their `message` and `data` are meant for the client. Errors returned by `useFetch` and `useAsyncData` are also unchanged, as they are part of the payload by design. Server routes (`server/api`) are not affected.
### Patches
Fixed in `nuxt@4.6.4`. Nuxt no…
Source: GitHub Security Advisories · 2026-11-16