VulnerabilityPublished 13 Aug 2026Updated 13 Nov 2026

CVE-2026-39365: Vite Vulnerable to Path Traversal

Affects viteSource GCVE Database

Compare

Authoritative record:CVE-2026-39365· Medium 6.3

Not known to be exploited · public detection template (Nuclei) · CVSS 6.3 Medium : upgrade to 8.0.5 when convenient.

Data as of 13 Nov 2026, 21:06 UTC

CVSS 4.0 base score

6.3Medium

How severe the flaw is on the 0–10 CVSS scale.

Patch: Available – fixed in 8.0.5

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

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: Present
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: None
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: Present: The successful attack depends on the presence of specific deployment and execution conditions of the vulnerable system that enable the attack. These include: a race condition must be won to successfully exploit the vulnerability (the successfulness of the attack is conditioned on execution conditions that are not under full control of the attacker, or the attack may need to be launched multiple times against a single target before being successful); the attacker must inject themselves into the logical network path between the target and the resource requested by the victim (e.g. vulnerabilities requiring an on-path attacker).
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 7 Apr 2026
Detectable: evidence found.
nuclei template: Vite Dev Server - Path Traversal in Optimized Deps .map Handling
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: evidence found.
3 exposed hosts found; no attack traffic recorded

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

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade vite to 8.0.5.

Affected software

Product	Affected	Fixed in
Homebrewvite`pkg:brew/vite`Other threats	Affected >=2.5.1 <8.0.5	Fixed in 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

Upgrade Vite to version 8.0.5 or later, where this path traversal vulnerability is fixed. Until patched, avoid exposing the Vite dev server to the network using the --host or server.host options if sensitive .map files exist. The vendor advisory confirms a patch is available and remediation is to update to the fixed version.

Description

Vite versions from 2.5.1 up to but not including 8.0.5 have a path traversal vulnerability in the dev server's handling of optimized dependency source map (.map) files. This flaw allows an attacker to retrieve .map files located outside the project root by exploiting insufficient path sanitization, bypassing the server's filesystem strict allow list. The vulnerability only affects applications that expose the Vite dev server to the network and have sensitive .map files with predictable paths. A fix is available in version 8.0.5.

Impact

An attacker can retrieve arbitrary .map files located outside the project root directory on a Vite dev server exposed to the network. This could lead to disclosure of sensitive source map files if their paths are predictable and the files contain sensitive content. The impact is limited to development environments where the dev server is exposed and sensitive .map files exist. There is no indication of remote code execution or broader compromise.

Summary

In Vite v7.3.1 and other affected versions (>=2.5.1 <8.0.5), the development server improperly handles requests for optimized dependency source map (.map) files. The server resolves file paths and reads files without properly restricting '../' path segments in the URL, enabling path traversal. This allows attackers to bypass the configured server.fs.strict allow list and access .map files outside the project root directory if those files contain valid source map JSON. The vulnerability requires the dev server to be explicitly exposed to the network (e.g., via --host option). A proof of concept demonstrates reading arbitrary .map files outside the project root by injecting '../' segments in the URL path. The issue is fixed in Vite 8.0.5.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 13 Nov 2026, 21:06 UTC

Public exploits and detectiona Nuclei detection template

Technical details

References

Community reviews

Related threats