Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-68155: CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in vitejs vite-plugin-react

0
High
VulnerabilityCVE-2025-68155cvecve-2025-68155cwe-22cwe-73
Published: Tue Dec 16 2025 (12/16/2025, 18:20:51 UTC)
Source: CVE Database V5
Vendor/Project: vitejs
Product: vite-plugin-react

Description

@vitejs/plugin-rs provides React Server Components (RSC) support for Vite. Prior to version 0.5.8, the `/__vite_rsc_findSourceMapURL` endpoint in `@vitejs/plugin-rsc` allows unauthenticated arbitrary file read during development mode. An attacker can read any file accessible to the Node.js process by sending a crafted HTTP request with a `file://` URL in the `filename` query parameter. Version 0.5.8 fixes the issue.

AI-Powered Analysis

AILast updated: 12/16/2025, 18:39:58 UTC

Technical Analysis

CVE-2025-68155 is a path traversal vulnerability (CWE-22) found in the @vitejs/plugin-rsc component of the vite-plugin-react package used with the Vite build tool. This vulnerability exists in versions prior to 0.5.8 and manifests in the /__vite_rsc_findSourceMapURL HTTP endpoint, which is intended to support React Server Components (RSC) during development. The flaw allows unauthenticated attackers to craft HTTP requests containing a file:// URL in the filename query parameter, enabling arbitrary file read access to any file accessible by the Node.js process on the server. Since this occurs in development mode, it is typically exposed on developer machines or development servers that may be accessible within internal networks or, if misconfigured, externally. The vulnerability does not require authentication or user interaction, making exploitation straightforward if the endpoint is reachable. The impact is primarily confidentiality loss, as attackers can read sensitive files such as environment variables, source code, or credentials. The vulnerability was assigned a CVSS 3.1 score of 7.5 (high severity) due to its network attack vector, lack of required privileges, and high confidentiality impact. The issue was addressed in vite-plugin-react version 0.5.8 by properly restricting file access and sanitizing input parameters to prevent path traversal. No known exploits have been reported in the wild as of the publication date. However, the risk remains significant for organizations using vulnerable versions in development environments accessible to untrusted users.

Potential Impact

For European organizations, this vulnerability poses a significant risk to the confidentiality of sensitive development data. Exposure of source code, configuration files, API keys, or credentials could lead to further compromise, including intellectual property theft or escalation to production environments. Organizations using Vite and vite-plugin-react in their development pipelines, especially those with publicly accessible or poorly segmented development servers, are at risk. The impact is heightened for companies in sectors with strict data protection requirements such as finance, healthcare, and critical infrastructure, where leakage of sensitive information could have regulatory and reputational consequences. Additionally, the vulnerability could facilitate lateral movement within corporate networks if attackers gain access to internal development environments. Although the vulnerability does not affect production builds directly, the development environment exposure can be a stepping stone for more severe attacks.

Mitigation Recommendations

The primary mitigation is to upgrade vite-plugin-react to version 0.5.8 or later, which contains the patch preventing path traversal. Organizations should audit their development environments to ensure no vulnerable versions are in use. Access to development servers running Vite should be strictly controlled and limited to trusted internal users, ideally isolated from external networks via VPNs or firewalls. Implement network segmentation to prevent unauthorized access to development tools. Additionally, monitor HTTP endpoints for suspicious requests containing file:// URLs or unusual query parameters. Employ runtime application self-protection (RASP) or web application firewalls (WAFs) capable of detecting and blocking path traversal attempts. Developers should avoid exposing development servers publicly and use environment variables or secure vaults to manage sensitive data instead of relying on local files. Regularly review and update dependencies to incorporate security patches promptly.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2025-12-15T23:02:17.603Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 6941a4041a61eff6269a9351

Added to database: 12/16/2025, 6:25:08 PM

Last enriched: 12/16/2025, 6:39:58 PM

Last updated: 12/17/2025, 1:03:03 AM

Views: 15

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats