Skip to main content
VulnerabilityPublished

CVE-2026-128075: Nuxt exposes the message and data of unhandled errors thrown during server rendering

Affects nuxtSource GCVE Database

0
Compare
Authoritative record:CVE-2026-128075· Medium 5.3

Not known to be exploited · CVSS 5.3 Medium : upgrade to 4.6.4 when convenient.

Data as of 16 Nov 2026, 15:21 UTC

CVSS 3.1 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.15.3
Patch
Available – fixed in 4.6.4
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 13 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.

What to do

Upgrade nuxt to 4.6.4.

Affected software

ProductAffectedFixed in
npmnuxtAffected
  • >=4.0.0 <4.6.4
Fixed in
  • 4.6.4
npmnuxtAffected
  • >=3.0.0
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available in Nuxt version 4.6.4 that fixes this issue by marking unhandled errors to return generic messages instead of sensitive details. Users should upgrade to Nuxt 4.6.4 or later. Nuxt 3 is end-of-life and will not receive a fix; users should upgrade to Nuxt 4 or apply workarounds. Workarounds include catching errors from server-side requests and rethrowing sanitized errors using createError with safe messages, or deploying a Nitro plugin to hide error details in wrapped errors. If secrets such as tokens may have been exposed, rotate them promptly.

Description

Nuxt versions 3.x and 4.0.0 up to but not including 4.6.4 expose the message and data of unhandled errors thrown during server rendering to clients. This occurs when errors not explicitly created as HTTP errors propagate to the error page, causing sensitive information such as internal error messages, upstream response bodies, or tokens in URLs to be included in the client-visible payload. The issue is fixed in Nuxt 4.6.4 by marking such errors as unhandled and returning generic messages instead. Nuxt 3 is end-of-life and will not receive a fix. Workarounds include catching and rethrowing errors with sanitized messages or using a Nitro plugin to hide error details. If secrets were exposed, rotation is recommended.

References

Community reviews

Loading reviews…