
Loading

Loading
We use strictly necessary cookies to run this site, and analytics cookies to understand how it's used. See our Privacy Policy for details.
A GitHub-reviewed security advisory, not necessarily under active exploitation the way our CISA KEV advisories are, but a real, disclosed vulnerability in an open-source dependency.
Affected packages
Vulnerable: >= 4.0.0, < 4.6.4
Patched in 4.6.4
Vulnerable: >= 3.0.0, < 4.0.0
Details
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.
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.
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.
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.
Thanks to abhijit_dave for reporting this through the Vercel HackerOne program.
EPSS, exploit probability
Low0.31%
estimated chance of real-world exploitation in the next 30 days, higher than 24.3% of every CVE FIRST.org scores
Refreshed 11/16/2026, via FIRST.org's EPSS model, not CVSS, this measures likelihood of exploitation, not how severe it would be.
More npm advisories
Talk to us about this
Find out whether this dependency (or others like it) is actually reachable in your codebase.
Get help patching, or building dependency-scanning into your pipeline going forward.
A secure code review or supply chain review finds this before an advisory does.