Nuxt exposes the message and data of unhandled errors thrown during server rendering
Published 16 Nov 2026 · Updated 16 Nov 2026
Is your project on an affected nuxt?
Look after several JavaScript apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected packages
- Affected
- >=4.0.0 <4.6.4
- Fixed in
- 4.6.4
npm install nuxt@4.6.4- Affected
- >=3.0.0
- Fixed in
- No fix released
Details
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:
<script setup lang="ts">
const route = useRoute()
// the upstream error body, and the token in the URL, reach the client if this request fails
await $fetch(`http://users.internal/users/${route.params.id}?token=${useRuntimeConfig().usersToken}`)
</script>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 now marks any thrown value that is not already an HTTP error as unhandled, so the error page and JSON responses receive its status and a generic message. As a result, the error page no longer shows the message of an error thrown with throw new Error(...) in production; throw a createError with what the client may see instead.
Nuxt 3 has reached end of life and will not receive a fix. Upgrade to Nuxt 4, or apply the workaround below.
Workarounds
Catch errors from server-side requests and rethrow them with only the details the client may see:
try {
await $fetch(url)
} catch (error) {
throw createError({ statusCode: 502, statusMessage: 'Upstream request failed' })
}Alternatively, add a Nitro plugin that hides the details of errors Nuxt wrapped. This also hides the details of a createError called with an Error (or with a cause):
// server/plugins/hide-error-details.ts
export default defineNitroPlugin((nitroApp) => {
nitroApp.hooks.hook('error', (error) => {
const cause = (error as { cause?: unknown }).cause
if (cause instanceof Error && !(cause.constructor as { __h3_error__?: boolean }).__h3_error__) {
Object.assign(error, { unhandled: true, data: undefined })
}
})
})If secrets such as tokens in upstream URLs may have been exposed this way, rotate them.
Credits
Thanks to abhijit_dave for reporting this through the Vercel HackerOne program.
Is GHSA-96x6-fvhx-49hg in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected nuxt, and gives you the command that fixes it.
More advisories for nuxt
- LowCVE-2026-128076Nuxt: Colliding island props can share one `/__nuxt_island` path (incomplete fix for CVE-2026-46342) · 16 Nov 2026
- MediumCVE-2026-128074Nuxt payload URL generation has quadratic cost for repeated slashes in the request path · 16 Nov 2026
- MediumCVE-2026-128071Nuxt: Incomplete fix for GHSA-6gq8-jgmh-3ffp: an encoded slash (`%2F`) in the request path bypasses route rules on catch-all page routes · 16 Nov 2026
- MediumCVE-2026-119200Nuxt: Dot segments in the request path bypass `server/middleware` path checks and server route rules on page routes · 30 Oct 2026
- MediumCVE-2026-114132Nuxt: Server-side route rules (`redirect`, `headers`, `proxy`, `ssr`) are skipped for case-variant paths when routing is case-insensitive · 22 Oct 2026
- MediumCVE-2026-114133Nuxt server islands render `useHeadSafe` input without sanitisation · 22 Oct 2026
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.