CVE-2025-68155: CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in vitejs vite-plugin-react
@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 Analysis
Technical Summary
CVE-2025-68155 is a path traversal vulnerability (CWE-22) found in the @vitejs/plugin-rsc component of the vite-plugin-react package, which provides React Server Components support for the Vite build tool. The vulnerability exists in versions prior to 0.5.8 and affects the /__vite_rsc_findSourceMapURL HTTP endpoint used during development mode. An attacker can send an unauthenticated HTTP request containing a crafted file:// URL in the filename query parameter, which the plugin improperly processes without sufficient validation or restriction. This allows the attacker to read arbitrary files on the server that the Node.js process has access to, potentially exposing sensitive source code, configuration files, environment variables, or other confidential data. The vulnerability does not require any authentication or user interaction, making it remotely exploitable over the network. The flaw arises from improper limitation of pathname to a restricted directory, allowing directory traversal beyond intended boundaries. The issue was addressed and fixed in version 0.5.8 of the plugin by implementing proper validation and restrictions on the filename parameter. No known exploits are currently reported in the wild, but the high CVSS score of 7.5 reflects the significant confidentiality impact and ease of exploitation. This vulnerability primarily affects development environments where the plugin is active and accessible, which may be exposed unintentionally or through misconfiguration.
Potential Impact
For European organizations, this vulnerability poses a significant risk of sensitive information disclosure during software development. Since the flaw allows unauthenticated arbitrary file reads, attackers could access source code, credentials, API keys, or internal configuration files, potentially facilitating further attacks such as privilege escalation or supply chain compromise. Organizations using Vite with vite-plugin-react versions prior to 0.5.8 in their development or staging environments are particularly vulnerable if these environments are accessible over the network without proper access controls. The impact is mainly on confidentiality, with no direct integrity or availability effects. However, leaked information could indirectly lead to more severe attacks. The risk is heightened in organizations with remote or cloud-based development setups where development servers might be exposed. European companies in sectors with high software development activity, including technology firms, financial institutions, and critical infrastructure providers, could face increased risk if vulnerable versions are in use. Compliance with data protection regulations like GDPR also raises the stakes, as unauthorized data exposure could lead to regulatory penalties.
Mitigation Recommendations
1. Upgrade vite-plugin-react to version 0.5.8 or later immediately to apply the patch that fixes the vulnerability. 2. Restrict network access to development servers running Vite and vite-plugin-react, ensuring they are not publicly accessible or exposed to untrusted networks. 3. Implement strict firewall rules and VPN requirements for accessing development environments. 4. Conduct audits of development infrastructure to identify any instances of vulnerable versions and remediate promptly. 5. Use environment segmentation to isolate development environments from production and sensitive data stores. 6. Monitor HTTP endpoints for suspicious requests targeting /__vite_rsc_findSourceMapURL or unusual file:// URL patterns. 7. Educate development teams about secure configuration practices and the risks of exposing development tools publicly. 8. Consider implementing runtime application self-protection (RASP) or web application firewalls (WAF) that can detect and block path traversal attempts. 9. Review and minimize file system permissions granted to Node.js processes to limit accessible files in case of exploitation.
Affected Countries
Germany, France, United Kingdom, Netherlands, Sweden, Ireland
CVE-2025-68155: CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in vitejs 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
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, which provides React Server Components support for the Vite build tool. The vulnerability exists in versions prior to 0.5.8 and affects the /__vite_rsc_findSourceMapURL HTTP endpoint used during development mode. An attacker can send an unauthenticated HTTP request containing a crafted file:// URL in the filename query parameter, which the plugin improperly processes without sufficient validation or restriction. This allows the attacker to read arbitrary files on the server that the Node.js process has access to, potentially exposing sensitive source code, configuration files, environment variables, or other confidential data. The vulnerability does not require any authentication or user interaction, making it remotely exploitable over the network. The flaw arises from improper limitation of pathname to a restricted directory, allowing directory traversal beyond intended boundaries. The issue was addressed and fixed in version 0.5.8 of the plugin by implementing proper validation and restrictions on the filename parameter. No known exploits are currently reported in the wild, but the high CVSS score of 7.5 reflects the significant confidentiality impact and ease of exploitation. This vulnerability primarily affects development environments where the plugin is active and accessible, which may be exposed unintentionally or through misconfiguration.
Potential Impact
For European organizations, this vulnerability poses a significant risk of sensitive information disclosure during software development. Since the flaw allows unauthenticated arbitrary file reads, attackers could access source code, credentials, API keys, or internal configuration files, potentially facilitating further attacks such as privilege escalation or supply chain compromise. Organizations using Vite with vite-plugin-react versions prior to 0.5.8 in their development or staging environments are particularly vulnerable if these environments are accessible over the network without proper access controls. The impact is mainly on confidentiality, with no direct integrity or availability effects. However, leaked information could indirectly lead to more severe attacks. The risk is heightened in organizations with remote or cloud-based development setups where development servers might be exposed. European companies in sectors with high software development activity, including technology firms, financial institutions, and critical infrastructure providers, could face increased risk if vulnerable versions are in use. Compliance with data protection regulations like GDPR also raises the stakes, as unauthorized data exposure could lead to regulatory penalties.
Mitigation Recommendations
1. Upgrade vite-plugin-react to version 0.5.8 or later immediately to apply the patch that fixes the vulnerability. 2. Restrict network access to development servers running Vite and vite-plugin-react, ensuring they are not publicly accessible or exposed to untrusted networks. 3. Implement strict firewall rules and VPN requirements for accessing development environments. 4. Conduct audits of development infrastructure to identify any instances of vulnerable versions and remediate promptly. 5. Use environment segmentation to isolate development environments from production and sensitive data stores. 6. Monitor HTTP endpoints for suspicious requests targeting /__vite_rsc_findSourceMapURL or unusual file:// URL patterns. 7. Educate development teams about secure configuration practices and the risks of exposing development tools publicly. 8. Consider implementing runtime application self-protection (RASP) or web application firewalls (WAF) that can detect and block path traversal attempts. 9. Review and minimize file system permissions granted to Node.js processes to limit accessible files in case of exploitation.
Affected Countries
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/23/2025, 7:31:40 PM
Last updated: 2/7/2026, 1:30:27 PM
Views: 140
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2026-2085: Command Injection in D-Link DWR-M921
HighCVE-2026-2084: OS Command Injection in D-Link DIR-823X
HighCVE-2026-2083: SQL Injection in code-projects Social Networking Site
MediumCVE-2026-2082: OS Command Injection in D-Link DIR-823X
MediumCVE-2026-2080: Command Injection in UTT HiPER 810
HighActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.