S4E just found a medium-severity finding from leaked token-api key scanner
PlatformPlansPartners
Resources
ToolsBlogDocs
Sign Up →
medium·Product Based Web Vulnerabilities·Updated Apr 8, 2026

CVE-2026-39365 Scanner

CVE-2026-39365 Scanner - Path Traversal vulnerability in Vite Dev Server

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-2026-39365
6.3
CVSSmedium
Exploitable remotely over the internet · no authentication required.

Vite is a frontend tooling framework for JavaScript. From 6.0.0 to before 6.4.2, 7.3.2, and 8.0.5, 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 allow list and retrieve .map files located outside the project root, provided they can be parsed as valid source map JSON. This vulnerability is fixed in 6.4.2, 7.3.2, and 8.0.5.

Attack Vector
Network
Privileges Req.
None
User Interaction
None
Affected
viteby vitejs
>= 8.0.0, < 8.0.5
vite-plusby vitejs
< 0.1.16
Updated Aug 21, 2026View on NVD →
Detail

Vite Dev Server is an open-source development tool used primarily for building and serving JavaScript applications. It's favored by developers for its fast build times and efficient module handling, making it popular in modern web development projects. Primarily, it's utilized during the development phase of a project to assist in testing and debugging. Because it acts as a server, it features powerful serving capabilities for front-end web projects. The Vite Dev Server is often used in conjunction with modern JavaScript frameworks, enhancing their development experience. Robust and flexible, Vite is a choice for developers seeking efficient builds and development feedback loops.

The Path Traversal vulnerability identified in the Vite Dev Server arises from an improper handling of .map files via the optimized dependencies sourcemap handler. This vulnerability permits attackers to navigate the filesystem directory structure using path traversal techniques such as sequences of "../". Unauthorized users can potentially exploit this flaw to access files outside of the intended directory scope. Such exposure can lead to the disclosure of sensitive information stored on the server, which should be confined to restricted areas. While the problem primarily concerns development server instances exposed to the network, it emphasizes the importance of safe configuration practices.

Technically, the vulnerability is prominent in the dev server's mechanism of handling .map requests, where the path resolution process does not adequately restrict the use of traversal sequences. The dev server utilizes a combination of functionsnormalizePath(path.resolve(root, url.slice(1)))but fails to adequately sanitize paths, allowing the mapping to illegitimate sources. The critical flaw lies in the dev server allowing "../" segments in URL paths, which, when followed, could link beyond the project root. As a result, attackers might retrieve sourcemaps for files outside the root, revealing absolute filesystem paths.

Possible repercussions of exploiting this vulnerability can be severe, leading to unauthorized access to sensitive code or configuration details. By gaining the contents of .map files, attackers could uncover information potentially revealing the structure of the server-side application or data that wasn't meant for public disclosure. This not only raises privacy concerns but might also provide entry points for further attacks, leveraging the disclosed information. Developers are cautioned to take immediate action by upgrading to secure versions to mitigate any potential threats.

REFERENCES

Solution Advice
  • Upgrade Vite to version 8.0.5, 7.3.2, 6.4.2 or later.
  • Ensure development servers are not exposed to the network unless absolutely necessary, and employ proper firewall rules.
  • Implement additional validation on URL paths to prevent directory traversal attacks.
  • Limit file access permissions to essential directories only to minimize potential damage.
  • Regularly audit server configurations and update as part of a standard security protocol.

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.