CVE-2026-128075: Sensitive Information Disclosure via Unhandled SSR Errors in Nuxt
Vulnerability ID: CVE-2026-128075
CVSS Score: 5.3
Published: 2026-11-16
CVE-2026-128075 (GHSA-96x6-fvhx-49hg) is an information disclosure vulnerability in the Nuxt framework affecting versions 3.0.0 prior to 4.6.4. During Server-Side Rendering (SSR), unhandled non-HTTP exceptions thrown within pages, plugins, or route middleware are automatically wrapped using createError without being flagged as unhandled. Consequently, the production SSR serializer treats these internal exceptions as deliberate public HTTP errors and embeds their raw message and data properties—which frequently contain internal URLs, API credentials, and upstream response payloads—directly into the client-accessible NUXT_DATA hydration state and JSON error responses.
TL;DR
Nuxt versions 3.0.0 to 4.6.3 fail to mark auto-wrapped SSR exceptions as unhandled in production, exposing sensitive internal error messages, upstream URLs, and API tokens in the client-side NUXT_DATA payload.
Technical Details
- CVE ID: CVE-2026-128075 (GHSA-96x6-fvhx-49hg)
- Weakness Class: CWE-209: Generation of Error Message Containing Sensitive Information
- CVSS v3.1 Score: 5.3 Medium (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N)
- EPSS Score: 0.31% (24.31st Percentile)
- Affected Versions: nuxt >= 3.0.0, < 4.6.4
- Patched Version: nuxt 4.6.4 (Nuxt 3 is EOL)
- Attack Vector: Unauthenticated Network HTTP Request triggering SSR Exception
- CISA KEV Status: Not Listed
Affected Systems
- nuxt (npm package) >= 3.0.0, < 4.6.4
- Nuxt 3.x series (>= 3.0.0, < 4.0.0 - End of Life)
- Nuxt 4.x series (>= 4.0.0, < 4.6.4)
- nuxt: >= 3.0.0, < 4.0.0 (Fixed in:
None (End-of-Life; upgrade to 4.6.4)) - nuxt: >= 4.0.0, < 4.6.4 (Fixed in:
4.6.4)
Code Analysis
Commit: 8c56b71
Ensure createErrorFromThrown marks non-HTTP errors as unhandled in production and sanitize unhandled error status text during SSR rendering
Mitigation Strategies
- Upgrade Nuxt to version 4.6.4 or later to ensure unhandled SSR exceptions are properly flagged with unhandled: true in production.
- Deploy a global Nitro error plugin (server/plugins/hide-error-details.ts) for End-of-Life Nuxt 3 applications to strip error.data and enforce unhandled: true on wrapped non-H3 errors.
- Pass upstream API credentials via HTTP request headers (such as Authorization) rather than URL query strings so that URLs included in error messages do not contain plaintext secrets.
- Wrap sensitive SSR operations and $fetch calls in explicit try/catch blocks and throw sanitized createError objects.
Remediation Steps:
- Update package.json to require nuxt >= 4.6.4 and run npm install, pnpm update, or yarn upgrade.
- If running Nuxt 3.x (EOL), create server/plugins/hide-error-details.ts with a nitroApp.hooks.hook('error', ...) handler to mark auto-wrapped errors as unhandled.
- Audit useFetch and $fetch calls across pages, plugins, and middleware to ensure sensitive tokens are not embedded in request URLs.
- Rotate any internal API keys, query-string tokens, or credentials that may have been leaked in NUXT_DATA payloads prior to remediation.
References
- GitHub Security Advisory: GHSA-96x6-fvhx-49hg
- National Vulnerability Database: CVE-2026-128075
- CVE.org Record: CVE-2026-128075
- Nuxt Patch Commit 8c56b71e4d0377c5c047799078db09c6b3d4fde5
- Nuxt v4.6.4 Release
- CVEListV5 JSON Record for CVE-2026-128075
- FIRST EPSS Score Data for CVE-2026-128075
Read the full report for CVE-2026-128075 on our website for more details including interactive diagrams and full exploit analysis.

