Skip to main content
VulnerabilityPublished Updated

CVE-2026-39365: vitejs vite · Path Traversal

Affects vitejs viteSource CVE Database V5

0
Compare

Not known to be exploited · public detection template (Nuclei) · CVSS 6.3 Medium · fixed in 8.0.5 : update vitejs vite when convenient.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 4.0 base score
6.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.9% chance of exploitation in 30 days – higher than 60% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 8.0.5, 7.3.2, 6.4.2 +1
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 7 Apr 2026

  2. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

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

    Not in CISA KEV and no source reports exploitation

  4. 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 30 Oct 2026.

What to do

Upgrade vite to 8.0.5, 7.3.2 or 6.4.2; vite-plus to 0.1.16.

Affected software

ProductAffectedFixed in
vitejsviteAffected
  • >=8.0.0 <8.0.5
Fixed in
  • 8.0.5
vitejsviteAffected
  • >=7.0.0 <7.3.2
Fixed in
  • 7.3.2
vitejsviteAffected
  • >=6.0.0 <6.4.2
Fixed in
  • 6.4.2
vitejsvite-plusAffected
  • <0.1.16
Fixed in
  • 0.1.16
npmvitepkg:npm/viteOther threatsAffected
  • <6.4.2
  • <7.3.2
  • <8.0.5
Fixed in
  • 6.4.2
  • 7.3.2
  • 8.0.5

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

AI-suggested

This vulnerability is fixed in vite versions 6.4.2, 7.3.2, and 8.0.5. Users should upgrade to one of these versions or later to remediate the issue. Patch status is confirmed by the version fixes listed in the vulnerability description. No additional vendor advisory was provided. No mitigation other than upgrading is indicated.

Description

### Summary Any files ending with `.map` even out side the project can be returned to the browser. ### Impact Only apps that match the following conditions are affected: - explicitly exposes the Vite dev server to the network (using `--host` or [`server.host` config option](https://vitejs.dev/config/server-options.html#server-host)) - have a sensitive content in files ending with `.map` and the path is predictable ### Details In Vite v7.3.1, the dev server’s handling of `.map` requests for optimized dependencies resolves file paths and calls `readFile` without restricting `../` segments in the URL. As a result, it is possible to bypass the [`server.fs.strict`](https://vite.dev/config/server-options#server-fs-strict) allow list and retrieve `.map` files located outside the project root, provided they can be parsed as valid source map JSON. ### PoC 1. Create a minimal PoC sourcemap outside the project root ```bash cat > /tmp/poc.map <<'EOF' {"version":3,"file":"x.js","sources":[],"names":[],"mappings":""} EOF ``` 2. Start the Vite dev server (example) ```bash pnpm -C playground/fs-serve dev --host 127.0.0.1 --port 18080 ``` 3. Confirm that direct `/@fs` access is blocked by `strict` (returns 403) <img width="4004" height="1038" alt="image" src="https://github.com/user-attachments/assets/15a859a8-1dc6-4105-8d58-80527c0dd9ab" /> 4. Inject `../` segments under the optimized deps `.map` URL prefix to reach `/tmp/poc.map` <img width="2790" height="846" alt="image" src="https://github.com/user-attachments/assets/5d02957d-2e6a-4c45-9819-3f024e0e81f2" />

References

Community reviews

Loading reviews…