VulnerabilityPublished 20 Oct 2025

CVE-2025-62522: vitejs vite · Path Traversal

Affects vitejs viteSource CVE Database V5

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

Data as of 26 Oct 2026, 12:55 UTC

CVSS 4.0 base score

6.0Medium

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

EPSS: 1.0% chance of exploitation in 30 days – higher than 64% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 7.1.11, 7.0.8, 6.4.1 +4

CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: Present
Privileges Required: None
User Interaction: Passive
Vulnerable system confidentiality: High
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: Passive: Successful exploitation of this vulnerability requires limited interaction by the targeted user with the vulnerable system and the attacker’s payload. These interactions would be considered involuntary and do not require that the user actively subvert protections built into the vulnerable system.
Vulnerable system confidentiality: High: There is a total loss of confidentiality, resulting in all information within the Vulnerable System being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact. For example, an attacker steals the administrator's password, or private encryption keys of a web server.
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 20 Oct 2025
Detectable: evidence found.
nuclei template: Vite - Information Disclosure
Weaponised: 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: 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 26 Oct 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.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, 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 to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
npmvite`pkg:npm/vite`Other threats	Affected >=2.9.18 <3.0.0 >=3.2.9 <4.0.0 >=4.5.3 <5.0.0 >=5.2.6 <5.4.21 >=6.0.0 <6.4.1 >=7.0.0 <7.0.8 >=7.1.0 <7.1.11	Fixed in 3.0.0 4.0.0 5.0.0 5.4.21 6.4.1 7.0.8 7.1.11

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

AI-suggested

European organizations should take the following specific mitigation steps: 1) Immediately upgrade all Vite instances to the patched versions 5.4.21, 6.4.1, 7.0.8, or 7.1.11 depending on their current version. 2) Audit development environments to ensure that Vite dev servers are not unnecessarily exposed to external networks, especially on Windows hosts. 3) Implement network segmentation and firewall rules to restrict access to development servers to trusted internal IPs only. 4) Educate developers about the risks of exposing dev servers and enforce policies to avoid such exposure. 5) Review server.fs.deny configurations and verify that access controls are correctly enforced post-patch. 6) Monitor network traffic and logs for suspicious requests with trailing backslashes or unusual URL patterns targeting dev servers. 7) Consider using containerized or virtualized development environments with limited network exposure. 8) Integrate vulnerability scanning into CI/CD pipelines to detect usage of vulnerable Vite versions. These measures go beyond generic advice by focusing on environment hardening, developer awareness, and proactive monitoring specific to this vulnerability's exploitation vector.

Description

### Summary Files denied by [`server.fs.deny`](https://vitejs.dev/config/server-options.html#server-fs-deny) were sent if the URL ended with `\` when the dev server is running on Windows. ### 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)) - running the dev server on Windows ### Details `server.fs.deny` can contain patterns matching against files (by default it includes `.env`, `.env.*`, `*.{crt,pem}` as such patterns). These patterns were able to bypass by using a back slash(`\`). The root cause is that `fs.readFile('/foo.png/')` loads `/foo.png`. ### PoC ```shell npm create vite@latest cd vite-project/ cat "secret" > .env npm install npm run dev curl --request-target /.env\ http://localhost:5173 ``` <img width="1593" height="616" alt="image" src="https://github.com/user-attachments/assets/36212f4e-1d3c-4686-b16f-16b35ca9e175" />

Impact

For European organizations, the primary impact of CVE-2025-62522 lies in the potential unauthorized disclosure of sensitive files during development phases when the Vite dev server is exposed externally on Windows machines. This could lead to leakage of source code, configuration files, environment variables, or other sensitive data that may reside in restricted directories. Such information disclosure can facilitate further attacks, including credential theft, intellectual property loss, or supply chain compromise. While the vulnerability does not directly affect production environments, many organizations use Vite in local or staging environments that may be inadvertently exposed due to misconfiguration or developer practices. The impact is heightened in organizations with remote or hybrid development teams that expose dev servers to the network for collaboration. Given the widespread adoption of Vite in frontend development across Europe, especially in technology hubs and enterprises with modern web stacks, the risk is non-negligible. However, the requirement for Windows-based dev servers and explicit network exposure limits the scope somewhat. Still, failure to patch could result in data breaches and compliance violations under GDPR if personal or sensitive data is exposed.

Summary

CVE-2025-62522 is a path traversal vulnerability classified under CWE-22 found in the Vite frontend tooling framework for JavaScript. This vulnerability affects multiple version ranges of Vite, specifically from 2.9.18 up to but not including 3.0.0, 3.2.9 up to 4.0.0, 4.5.3 up to 5.0.0, 5.2.6 up to 5.4.21, 6.0.0 up to 6.4.1, 7.0.0 up to 7.0.8, and 7.1.0 up to 7.1.11. The issue arises when the Vite development server is running on Windows and is explicitly exposed to the network. In this scenario, if a URL ends with a backslash (\), the server improperly bypasses the server.fs.deny configuration, which is intended to restrict access to certain files or directories. Consequently, files that should be denied can be served to an attacker. The vulnerability exploits improper limitation of pathname to a restricted directory, allowing directory traversal beyond intended boundaries. Exploitation requires no authentication but does require user interaction to send a crafted URL. The vulnerability does not affect production builds or servers not exposed externally. The issue has been addressed in patched versions 5.4.21, 6.4.1, 7.0.8, and 7.1.11. No known exploits have been reported in the wild as of the publication date. The CVSS v4.0 base score is 6.0, reflecting network attack vector, low attack complexity, no privileges required, user interaction required, and high impact on confidentiality.

CWE-22Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #6OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
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.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
Architecture and Design
For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks…
Implementation · Input Validation
Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174).
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V12.3.1 (opens in a new tab)
Attack patterns
Path Traversal (opens in a new tab)
Using Slashes and URL Encoding Combined to Bypass Validation Logic (opens in a new tab)
Manipulating Web Input to File System Calls (opens in a new tab)
Using Escaped Slashes in Alternate Encoding (opens in a new tab)
Using Slashes in Alternate Encoding (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 20 Oct 2025, 20:13 UTC

Public exploits and detectiona Nuclei detection template

WeaknessesCWE-22

Technical details

References

Community reviews

Related threats