The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsLearn about Information Exposure vulnerabilities in an interactive lesson.
Start learningUpgrade nuxt to version 4.0.0, 4.6.4 or higher.
Affected versions of this package are vulnerable to Information Exposure via the server-side error handling path in createErrorFromThrown, when a page, plugin, or route middleware throws a non-HTTP error during server rendering. Nuxt wraps the thrown value with createError and incorrectly treats it as an error deliberately exposed by the application, causing the original message and data to be included in the error page payload (__NUXT_DATA__) and JSON error responses in production. An attacker who can trigger a server-side error - for example by supplying an input that causes a $fetch call to fail - receives the full upstream error message and data, which may include internal URLs, query-string secrets, response bodies, or database host names, regardless of what a custom error.vue renders.
Note: Errors created deliberately with createError or showError, errors returned by useFetch or useAsyncData, and server/api routes are not affected.
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 (server/plugins/hide-error-details.ts) that sets unhandled: true and clears data on any error whose cause is a non-h3 Error instance.