Advisory

GHSA-96x6-fvhx-49hg

Also known as: CVE-2026-128075

Summary

Nuxt exposes the message and data of unhandled errors thrown during server rendering

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 [email protected]. 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.

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2026-11-16 15:01 UTC
Modified
2026-11-16 15:15 UTC

Affected packages and fixes

nuxt

npm · All systems

Affected

  • introduced 4.0.0, fixed 4.6.4 (semver)

Fixed versions

4.6.4

Fix

nuxt

npm · All systems

Affected

  • introduced 3.0.0 (semver)

Fixed versions

None listed

Fix

No fixed version is listed.

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences