CVE-2026-128075 — Nuxt — CWE-209
CVE-2026-128075 is a MEDIUM severity security vulnerability (CWE-209) (CVSS 5.3/10 (EPSS: 0.3%)) affecting Nuxt. Technical vector analysis shows that an attacker can exploit this flaw remotely over the network without authentication (PR:N) with zero user interaction (UI:N), posing a direct security risk to affected deployments.
📄 Official NVD / MITRE Original Record Text
### 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: ```vue <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: th
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
CVE-2026-128075
CVSS 5.3/10 · MEDIUM · 16.11.2026
CWE: CWE-209
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
🎯 WHAT IS THIS VULNERABILITY?
Summary: ### 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…
Affected: nuxt
⚡ ATTACK CHAIN
Remotely over internet | no authentication required | no user interaction | low complexity.
🌍 REAL WORLD IMPACT
🛡️ REMEDIATION
→ Apply vendor security update for nuxt.
→ Pre-patch: put service behind VPN or apply IP allowlist.
→ Add WAF rule, create IDS alert for anomalous traffic.
⚠️ URGENCY
📋 Routine update cycle (30 days)
────────────────────────────────────────
[Kural Tabanlı Otomatik Güvenlik Analizi]