MediumCVE-2026-112946

    Vitejs: Path Traversal (CVE-2026-112946)

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

    What is affected, what to do

    Update Vitejs to version 6.4.4, Vite-plus to version 1.1.0.

    Affected
    • Vitejs gte 7.0.0, < 7.3.7..*
    • Vitejs lt *..6.4.4
    • Vite-plus lt *..1.1.0
    Fixed in
    • Vitejs 6.4.4
    • Vite-plus 1.1.0

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

    Metrics

    6.3

    Priority

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

    Source: Vendor (CNA), CVSS v4

    6.3

    CVSS v4

    Severity Medium on the scale from 0 to 10.

    Source: OSV, Hersteller, CVE.org

    0.9 %

    EPSS score

    Low — model estimates < 1% exploitation likelihood.

    Source: FIRST EPSS, percentile 58.2

    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
    88.63 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.3 Methodology
    CVSS v4

    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.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.9 %
    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
    58.2
    High — this CVE ranks above the median of all CVEs scored today (rank ≥ 36%).
    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: proof of concept · not automatable · Technical impact: partial
    Source: CISA Vulnrichment, as of 20 October 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-22, CWE-284

    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

    The content of files outside server.fs setting can be returned to the browser if the project imports a file path concatenated with the root. For example, if the project references <path-to-project-root>/etc/hosts, the content of /etc/hosts was possible to be returned.

    The content of files outside the server.fs.allow option can be returned to the browser when a project imports a file whose root-relative path matches an absolute path on the host. For example, referencing <project-root>/etc/hosts could make Vite return the host's /etc/hosts file.

    Impact

    Only apps that meet all of the following conditions are affected:

    • explicitly expose the Vite dev server to the network (using --host or the server.host option)
    • contain an imported file whose root-relative browser URL is also the absolute path of a readable file on the host
    • The sensitive file is not matched by server.fs.deny
    • the dev server is not running on Windows

    Details

    When Vite analyzes an in-root import, it rewrites the resolved module ID to a browser URL such as /etc/hostname. In affected versions, Vite converts that URL with fsPathFromUrl and adds the result to safeModulePaths. Because fsPathFromUrl ensures a leading slash without resolving the URL against the project root, the project URL /etc/hostname is recorded as if it were the absolute filesystem path /etc/hostname.

    For a later request to /@fs/etc/hostname, the raw-filesystem middleware interprets /etc/hostname as an absolute path. The access check applies server.fs.deny, then accepts paths present in safeModulePaths before checking server.fs.allow. As a result, the request can return the host file instead of the project file that originally populated safeModulePaths.

    PoC

    The following example requires Linux with a readable /etc/hostname:

    $ mkdir vite-safe-module-path-poc
    $ cd vite-safe-module-path-poc
    $ npm init -y
    $ npm install vite@8.3.1
    $ mkdir -p etc
    $ echo 'PROJECT-DECOY\n' > etc/hostname
    $ echo 'import "./etc/hostname"\n' > main.js
    $ npx vite --host 127.0.0.1
    

    In another terminal:

    $ curl -o /dev/null -s -w '%{http_code}\n' http://127.0.0.1:5173/main.js
    200
    $ curl -sS -o response -w '%{http_code}\n' http://127.0.0.1:5173/@fs/etc/hostname
    200
    $ cmp -s response /etc/hostname && echo 'response matches host file'
    response matches host file
    

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

    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
    vitejsvite
    • < 6.4.4
    • ≥ 7.0.0, < 7.3.7
    • 6.4.4
    • —
    vitejsvite-plus
    • < 1.1.0
    • 1.1.0
    npmvite
    • <= 6.4.3
    • 8.3.0
    • —
    • >= 8.2.0, <= 8.2.3
    • >= 8.0.0, <= 8.1.5
    • 8.2.0
    • >= 7.0.0, <= 7.3.6
    • 7.0.0
    • >= 8.3.0, <= 8.3.2
    • 8.0.0
    • 6.4.4
    • 8.3.3
    • 6.4.4
    • 8.2.4
    • 8.1.6
    • 8.2.4
    • 7.3.7
    • 7.3.7
    • 8.3.3
    • 8.1.6
    npmvite-plus
    • <= 1.0.0
    • —
    • 1.1.0
    • 1.1.0

    Vendors and products

    Weakness classes (CWE)

    • CWE-22Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

      Base

      The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.

      Entry at MITRE CWE-22
    • CWE-284Improper Access Control

      Pillar

      The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.

      Entry at MITRE CWE-284

    References & sources

    • github.comvitejs/vite/commit/170b92791421bcd484f7325936d989a82d6bd4aax_refsource_MISC, web
    • github.comvitejs/vite/commit/45c0e3392a298626955a0ab93a8e51232daac721x_refsource_MISC, web
    • github.comvitejs/vite/commit/c3e06f92e969952466b4e2f5801e85e1e00cd905x_refsource_MISC, web
    • github.comvitejs/vite/commit/e570d8d016096b5f8f6f09808376ca6cf73f27d0x_refsource_MISC, web
    • github.comvitejs/vite/commit/f0d76c7da13d5e794807b82f0b86c1931a8438e3x_refsource_MISC, web
    • github.comvitejs/vite/pull/23656x_refsource_MISC, web
    • github.comvitejs/vite/security/advisories/GHSA-rq7h-c2jc-7f22x_refsource_CONFIRM, web
    • NVD (NIST)vuln/detail/CVE-2026-112946advisory
    • github.comvitejs/vitepackage

    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. Record modifiedCISA ADP

      CISA assessment (SSVC): exploitation: proof of concept, automatable: no

      Show 2 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Referenceadded
      —
      https://github.com/vitejs/vite/security/advisories/GHSA-rq7h-c2jc-7f22
      SSVC assessmentadded
      —
      {"id":"CVE-2026-112946","role":"CISA Coordinator","options":[{"exploitation":"poc"},{"automatable":"no"},{"technicalImpact":"partial"}],"version":"2.0.3","timestamp":"2026-10-20T16:45:38.089794Z"}

      Source identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0

    2. ReceivedGitHub

      Show 12 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Descriptionadded
      —
      Vite is a frontend tooling framework for JavaScript. Prior to 6.4.4, 7.3.7, 8.1.6, 8.2.4, and 8.3.3, import analysis can record a root-relative browser URL in safeModulePaths instead of the cleaned resolved module identifier. On a network-accessible, non-Windows development server, an imported project file whose URL matches an absolute host path can authorize a later raw-filesystem request for that host file, provided server.fs.deny does not block it. The request can disclose the matching file outside the project root, but it does not allow arbitrary path traversal because the host path must correspond to a project-relative URL authorized by the application graph. This issue is fixed in versions 6.4.4, 7.3.7, 8.1.6, 8.2.4, and 8.3.3.
      CVSSadded
      —
      AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
      Weakness type (CWE)added
      —
      CWE-22
      Weakness type (CWE)added
      —
      CWE-284
      Affected versions (publisher)added
      —
      New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/112xxx/CVE-2026-112946.json">CVE-2026-112946</a>
      Referenceadded
      —
      https://github.com/vitejs/vite/commit/170b92791421bcd484f7325936d989a82d6bd4aa
      Referenceadded
      —
      https://github.com/vitejs/vite/commit/45c0e3392a298626955a0ab93a8e51232daac721
      Referenceadded
      —
      https://github.com/vitejs/vite/commit/c3e06f92e969952466b4e2f5801e85e1e00cd905
      Referenceadded
      —
      https://github.com/vitejs/vite/commit/e570d8d016096b5f8f6f09808376ca6cf73f27d0
      Referenceadded
      —
      https://github.com/vitejs/vite/commit/f0d76c7da13d5e794807b82f0b86c1931a8438e3
      Referenceadded
      —
      https://github.com/vitejs/vite/pull/23656
      Referenceadded
      —
      https://github.com/vitejs/vite/security/advisories/GHSA-rq7h-c2jc-7f22

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