MediumCVE-2026-128075

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

    Published Last modified Sources: OSV, EUVD, Hersteller, CVE.org

    Share

    What is affected, what to do

    Update nuxt to version 4.6.4.

    Affected
    • Nuxt gte 3.0.0, < 4.6.4..*

    Not sure whether and how you are affected? Ask a question about this vulnerability

    Metrics

    5.3

    XIEM Effective CVSS

    Highest available CVSS rating from NVD and vendor data.

    Source: Vendor (CNA), CVSS v3

    5.3

    CVSS v3

    Severity Medium on the scale from 0 to 10.

    Source: OSV, EUVD, Hersteller, CVE.org

    0.3 %

    EPSS score

    Low — model estimates < 1% exploitation likelihood.

    Source: FIRST EPSS, percentile 24.3

    Show all metrics
    Severity
    Medium
    Priority (0–325)

    The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?

    Read in glossary
    61.24 Methodology
    Exploit maturity

    An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.

    Read in glossary
    no public PoC known
    XIEM Effective CVSS

    XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.

    Read in glossary
    5.3 Methodology
    CVSS v3

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    5.3
    EPSS score

    The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.

    Read in glossary
    0.3 %
    Low — model estimates < 1% exploitation likelihood.
    EPSS percentile

    The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.

    Read in glossary
    24.3
    Elevated — this CVE ranks above at least 10% of all CVEs scored today.
    KEV status

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    —
    Published
    CISA assessment (SSVC)
    Exploitation: none known · automatable · Technical impact: partial
    Source: CISA Vulnrichment, as of 13 November 2026
    CWE

    CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.

    Read in glossary
    CWE-209

    Detection rules

    No NEOSEC detection rule is available for this vulnerability yet.

    Classification under NIS2 and CRA

    Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

    NIS2

    NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.

    Read in glossary
    Handle the vulnerability in regular vulnerability handling under Art. 21(2)(e) NIS2.
    CRA

    The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.

    Read in glossary
    From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
    ISO/IEC 27001

    ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.

    Read in glossary
    Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

    Description

    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:

    <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.

    Patches

    Fixed in nuxt@4.6.4. 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.

    Workarounds

    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.

    Credits

    Thanks to abhijit_dave for reporting this through the Vercel HackerOne program.

    Source: OSV (Open Source Vulnerabilities), ENISA EUVD, GitHub Security Advisories, cvelistv5, NVD (NIST), CVE.org (MITRE)

    Affected products

    The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

    Affected products
    Affected versionsFixed in
    nuxtnuxt
    • ≥ 3.0.0, < 4.6.4
    • —
    npmnuxt
    • 3.0.0
    • >= 3.0.0, < 4.0.0
    • >= 4.0.0, < 4.6.4
    • 4.0.0
    • —
    • —
    • 4.6.4
    • 4.6.4

    Vendors and products

    Weakness classes (CWE)

    • CWE-209Generation of Error Message Containing Sensitive Information

      Base

      The product generates an error message that includes sensitive information about its environment, users, or associated data.

      Entry at MITRE CWE-209

    References & sources

    • github.comnuxt/nuxt/security/advisories/GHSA-96x6-fvhx-49hgeuvd, x_refsource_CONFIRM, web
    • github.comnuxt/nuxt/commit/8c56b71e4d0377c5c047799078db09c6b3d4fde5euvd, x_refsource_MISC, web
    • github.comnuxt/nuxt/releases/tag/v4.6.4euvd, x_refsource_MISC, web
    • NVD (NIST)vuln/detail/CVE-2026-128075euvd, advisory
    • github.comnuxt/nuxtpackage

    Changes to this CVE

    Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).

    1. ReceivedGitHub

      Show 7 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Descriptionadded
      —
      Nuxt is an open-source web development framework for Vue.js. From 3.0.0 until 4.6.4, Nuxt wraps non-HTTP errors thrown during server rendering with createError and incorrectly treats the result as an error deliberately exposed by the application. In production, the error page payload (__NUXT_DATA__) and JSON error response can therefore disclose the original message and data, including an upstream $fetch URL, query-string secrets, response bodies, database hosts, or similar sensitive details, regardless of what a custom error.vue renders. Errors deliberately created with createError or showError, errors returned by useFetch or useAsyncData, and server/api routes are not affected because their client-visible behavior is intentional or follows a different path. This issue is fixed in version 4.6.4.
      CVSSadded
      —
      AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
      Weakness type (CWE)added
      —
      CWE-209
      Affected versions (publisher)added
      —
      New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/128xxx/CVE-2026-128075.json">CVE-2026-128075</a>
      Referenceadded
      —
      https://github.com/nuxt/nuxt/commit/8c56b71e4d0377c5c047799078db09c6b3d4fde5
      Referenceadded
      —
      https://github.com/nuxt/nuxt/releases/tag/v4.6.4
      Referenceadded
      —
      https://github.com/nuxt/nuxt/security/advisories/GHSA-96x6-fvhx-49hg

      Source identifier: security-advisories@github.com

    Embed badge

    Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

    Badge preview for CVE-2026-128075
    <a href="https://intel.neosec.eu/en/cve/CVE-2026-128075"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-128075.svg?lang=en" alt="CVE-2026-128075 – NEOSEC Intel" height="20"></a>