MediumCVE-2026-119200

    Nuxt: Improper Resolution of Path Equivalence (CVE-2026-119200)

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

    What is affected, what to do

    Update @nuxt/nitro-server to version 4.6.3, nuxt to version 4.6.3.

    Affected
    • Nuxt gte 4.6.0, < 4.6.3..*
    • Nuxt Nitro-server gte 4.6.0, < 4.6.3..*

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

    Metrics

    6.5

    Priority

    XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.

    Source: Vendor (CNA), CVSS v3

    6.5

    CVSS v3

    Severity Medium on the scale from 0 to 10.

    Source: OSV, Hersteller, CVE.org

    0.3 %

    EPSS score

    Low — model estimates < 1% exploitation likelihood.

    Source: FIRST EPSS, percentile 27.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
    68.48 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
    6.5 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
    6.5
    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
    27.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
    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-41, CWE-436, CWE-863

    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

    Since 4.6.0, Nuxt resolves . and .. segments in the request path, including percent-encoded forms such as %2e, before rendering a page. Nitro's routing, Nitro's route rules and server/middleware see the path with those segments still in place. A request for /%2e/admin therefore renders the page at /admin, while server-side checks keyed on /admin do not apply.

    Impact

    An unauthenticated attacker can bypass server-side controls that match on the request path of a page route.

    server/middleware that checks event.path (or event.node.req.url) is skipped:

    export default defineEventHandler((event) => {
      if (event.path.startsWith('/admin') && !isAuthenticated(event)) {
        throw createError({ statusCode: 401 })
      }
    })
    

    With this middleware, /admin returns 401, but /%2e/admin, /.%2e/admin and /x/%2e%2e/admin reach the middleware with event.path set to /./admin, /../admin and /x/../admin, and render app/pages/admin.vue along with the data it fetches during server rendering.

    Server-side redirect and headers route rules are skipped in the same way, so '/admin/**': { redirect: '/login' } does not redirect /%2e/admin/secret, and per-route security headers such as Content-Security-Policy are not sent.

    Not affected:

    • API handlers in server/api and server/routes. Nitro's router does not resolve dot segments, so these requests do not reach the handler.
    • appMiddleware route rules and middleware declared with definePageMeta, which are matched against the resolved route.
    • Nuxt 3.x and 4.0.0 to 4.5.x, which pass the path to the page router unchanged, so these requests 404.

    Browsers resolve dot segments before sending a request, so exploitation requires a client that sends the path as written.

    Patches

    Fixed in nuxt@4.6.3 and @nuxt/nitro-server@4.6.3. A page request whose path contains . or .. segments now receives a 404 instead of rendering the page the path resolves to, and route-rule keys and lookup paths have their dot segments resolved, including percent-encoded spellings, before they are compared.

    Workarounds

    Reject dot segments in a server middleware that runs before your other middleware (middleware runs in file name order):

    // server/middleware/0.dot-segments.ts
    export default defineEventHandler((event) => {
      if (/(?:^|\/)\.{1,2}(?:\/|$)/.test(event.path.split('?')[0])) {
        throw createError({ statusCode: 404 })
      }
    })
    

    Checking getRequestURL(event).pathname instead of event.path is not a sufficient workaround: it resolves dot segments, but keeps percent-encoding such as %61 that the page router decodes. Path checks in server middleware should also account for the page router matching paths case-insensitively unless router.options.sensitive is set.

    A reverse proxy or CDN that normalises the request path before forwarding it also removes the mismatch.

    Credits

    Thanks to @vinzabe, @nikhilagrawalsf (Nikhil Agrawal, Mettle Labs), @0xjunwei and @kq5y, who reported this issue independently.

    Source: OSV (Open Source Vulnerabilities), GitHub Security Advisories, NVD (NIST), cvelistv5

    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
    @nuxtnitro-server
    • ≥ 4.6.0, < 4.6.3
    • —
    nuxtnuxt
    • ≥ 4.6.0, < 4.6.3
    • —
    npm@nuxt/nitro-server
    • >= 4.6.0, < 4.6.3
    • 4.6.0
    • 4.6.3
    • 4.6.3
    npmnuxt
    • 4.6.0
    • >= 4.6.0, < 4.6.3
    • 4.6.3
    • 4.6.3

    Vendors and products

    Weakness classes (CWE)

    • CWE-41Improper Resolution of Path Equivalence

      Base

      The product is vulnerable to file system contents disclosure through path equivalence. Path equivalence involves the use of special characters in file and directory names. The associated manipulations are intended to generate multiple names for the same object.

      Entry at MITRE CWE-41
    • CWE-436Interpretation Conflict

      Class

      Product A handles inputs or steps differently than Product B, which causes A to perform incorrect actions based on its perception of B's state.

      Entry at MITRE CWE-436
    • CWE-863Incorrect Authorization

      Class

      The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.

      Entry at MITRE CWE-863

    References & sources

    • github.comnuxt/nuxt/commit/45463f8b58487e387149ebfb704d6a0834b3a450x_refsource_MISC, web
    • github.comnuxt/nuxt/releases/tag/v4.6.3x_refsource_MISC, web
    • github.comnuxt/nuxt/security/advisories/GHSA-9v7c-q64q-vv33x_refsource_CONFIRM, web
    • NVD (NIST)vuln/detail/CVE-2026-119200advisory
    • 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

      CVSS V3.1: AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

      Weakness type: CWE-436, CWE-41, CWE-863

      Description added or changed

      Show 9 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 4.6.0 until 4.6.3, Nuxt resolves literal or percent-encoded dot segments before rendering a page while Nitro routing, server/middleware checks, and server route rules evaluate the unresolved path. A request such as /%2e/admin can therefore render app/pages/admin.vue and its server-rendered data while checks keyed to /admin, redirects, or per-route security headers do not apply. API handlers, appMiddleware, Nuxt 3, and Nuxt 4.0.0 through 4.5.x are not affected, and exploitation requires a client that sends dot segments without browser normalization. This issue is fixed in version 4.6.3.
      CVSSadded
      —
      AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
      Weakness type (CWE)added
      —
      CWE-436
      Weakness type (CWE)added
      —
      CWE-41
      Weakness type (CWE)added
      —
      CWE-863
      Affected versions (publisher)added
      —
      New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/119xxx/CVE-2026-119200.json">CVE-2026-119200</a>
      Referenceadded
      —
      https://github.com/nuxt/nuxt/commit/45463f8b58487e387149ebfb704d6a0834b3a450
      Referenceadded
      —
      https://github.com/nuxt/nuxt/releases/tag/v4.6.3
      Referenceadded
      —
      https://github.com/nuxt/nuxt/security/advisories/GHSA-9v7c-q64q-vv33

      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-119200
    <a href="https://intel.neosec.eu/en/cve/CVE-2026-119200"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-119200.svg?lang=en" alt="CVE-2026-119200 – NEOSEC Intel" height="20"></a>