CVE-2025-62522

vite allows server.fs.deny bypass via backslash on Windows

Files denied by server.fs.deny were sent if the URL ended with \ when the dev server is running 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

npm create vite@latest
cd vite-project/
cat "secret" > .env
npm install
npm run dev
curl --request-target /.env\ http://localhost:5173

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)
• running the dev server on Windows

Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files. Typical impact: unauthorized file read or write outside the intended directory.

Kodem intelligence

Already deployed Kodem?

1. What is CVE-2025-62522? CVE-2025-62522 is a medium-severity path traversal vulnerability in vite (npm), affecting versions >= 7.1.0, <= 7.1.10. It is fixed in 7.1.11, 7.0.8, 6.4.1, 5.4.21. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.
2. Which versions of vite are affected by CVE-2025-62522? vite (npm) versions >= 7.1.0, <= 7.1.10 is affected.
3. Is there a fix for CVE-2025-62522? Yes. CVE-2025-62522 is fixed in 7.1.11, 7.0.8, 6.4.1, 5.4.21. Upgrade to this version or later.
4. Is CVE-2025-62522 exploitable, and should I be worried? Whether CVE-2025-62522 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
5. What actually determines whether CVE-2025-62522 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
6. How do I fix CVE-2025-62522?
   • Upgrade vite to 7.1.11 or later
   • Upgrade vite to 7.0.8 or later
   • Upgrade vite to 6.4.1 or later
   • Upgrade vite to 5.4.21 or later
   • Upgrade vite to 5.4.21 or later
   • Upgrade vite to 5.4.21 or later
   • Upgrade vite to 5.4.21 or later

Other vulnerabilities in vite