S4E just found a high-severity finding from ssl sweet32 vulnerability checker
PlatformPlansPartners
Resources
ToolsBlogDocs
Sign Up →
medium·Product Based Web Vulnerabilities·Updated May 5, 2026

CVE-2025-32395 Scanner

CVE-2025-32395 Scanner - Path Traversal vulnerability in Vite

Est. Time~10 seconds
Scan TypeSingle Scan
Targetsdomain, subdomain, ipv4
CostFree
2.8k
Times Used
continuous scan runs
5.8k
Continuously Checked
assets under CS
0
Vulnerabilities Found
confirmed findings
References
CVECVE-2025-32395
6.0
CVSSmedium
Exploitable remotely over the internet · no authentication required.

Vite is a frontend tooling framework for javascript. Prior to 6.2.6, 6.1.5, 6.0.15, 5.4.18, and 4.5.13, the contents of arbitrary files can be returned to the browser if the dev server is running on Node or Bun. HTTP 1.1 spec (RFC 9112) does not allow # in request-target. Although an attacker can send such a request. For those requests with an invalid request-line (it includes request-target), the spec recommends to reject them with 400 or 301. The same can be said for HTTP 2. On Node and Bun, those requests are not rejected internally and is passed to the user land. For those requests, the value of http.IncomingMessage.url contains #. Vite assumed req.url won't contain # when checking server.fs.deny, allowing those kinds of requests to bypass the check. Only apps explicitly exposing the Vite dev server to the network (using --host or server.host config option) and running the Vite dev server on runtimes that are not Deno (e.g. Node, Bun) are affected. This vulnerability is fixed in 6.2.6, 6.1.5, 6.0.15, 5.4.18, and 4.5.13.

Attack Vector
Network
Privileges Req.
None
User Interaction
P
Affected
viteby vitejs
>= 6.2.0, < 6.2.6
Updated Aug 22, 2026View on NVD →
Detail

The Vite development server is a popular tool used primarily by developers for building and serving web applications, especially those using modern JavaScript frameworks. It is often utilized during the development phase to enable efficient testing and debugging of applications. Vite's speed and hot module replacement features make it an attractive choice for developers aiming to improve their productivity. It supports various frontend frameworks like Vue.js, React, and others, offering a seamless development experience. Specifically crafted to boost the development workflow, Vite is highly favored in modern frontend development environments. Despite its benefits, it's crucial to ensure that Vite is properly secured when exposed to networks during the development process.

The path traversal vulnerability in Vite arises due to improper handling of request URLs containing specific characters, such as '#', on its development server. This security flaw allows unauthorized users to access files beyond the intended directory scope. When misconfigured or exposed inadvertently during development, the server can be an easy target for attackers. This vulnerability is particularly impactful because it does not require authentication, making it accessible to anyone who can connect to the server. Ensuring Vite is configured correctly and updated to the latest secure version is imperative to mitigate such risks.

Technically, the vulnerability can be triggered by sending a crafted HTTP request with a path containing traversals to the Vite server. By exploiting this flaw, an attacker can escape the web root directory and access sensitive files on the hosting filesystem. This attack technique, leveraging path traversal, can be adjusted depending on the file structure, targeting significant configuration or secret files. The flaw heavily relies on the assumption that the server is running in an exposed network environment, allowing the crafted requests to be successfully delivered. It's crucial for developers to ensure that their Vite servers are not unnecessarily exposed to reduce such risks.

If this vulnerability is exploited, unauthorized users might gain access to sensitive files, which could contain critical configuration information or other sensitive data. This could lead to further attacks, including data theft, system takeovers, or facilitating further penetration into the network. It's especially risky for organizations that inadvertently leave development servers exposed due to misconfigurations. The effect of such an exploit can compromise the confidentiality of data and can also be a stepping stone for attackers aiming to gain broader access to the infrastructure.

REFERENCES

Solution Advice
  • Update to Vite versions 6.2.6, 6.1.5, 6.0.15, 5.4.18, or 4.5.13 or later to address the vulnerability.
  • Ensure Vite development servers are not exposed to unauthorized environments and limit their IP whitelisting.
  • Implement network-level security measures to restrict access to development servers during their use.
  • Regularly audit server configurations to identify any inadvertent exposure or misconfiguration.
  • Consider deploying web application firewalls to monitor and filter incoming traffic to development servers.

Get AI-powered remediation steps tailored to your asset.

Try AI Solutions →

Check your infrastructure.
Right now.

11,000+ scanners. Free to start. No credit card required.