@vitejs/plugin-rsc has an Arbitrary File Read via /__vite_rsc_findSourceMapURL Endpoint
CVE-2025-68155GHSA-g239-q96q-x4qm
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (@vitejs/plugin-rsc 0.5.8), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
- Affected
- < 0.5.8
- Fixed in
- 0.5.8
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-g239-q96q-x4qm lists affected ranges: npm @vitejs/plugin-rsc >=0 <0.5.8 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-g239-q96q-x4qm lists affected ranges: npm @vitejs/plugin-rsc >=0 <0.5.8
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
- EPSS
- CVE-2025-68155: 0.50% estimated exploitation activity in the next 30 days; percentile 43.05 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Summary The /viterscfindSourceMapURL 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. Severity: High Attack Vector: Network Privileges Required: None Scope: Development mode only (vite dev) --- Impact Who Is Affected? - All developers using @vitejs/plugin-rsc during development - Projects running vite dev with the RSC plugin enabled Attack Scenarios 1. Network-Exposed Dev Servers: When developers run vite --host 0.0.0.0 (common for mobile testing), attackers on the same network can read files. 2. ~XSS-Based Attacks:~ ~If the application has an XSS vulnerability, malicious JavaScript can fetch sensitive files and exfiltrate them.~ 3. ~Malicious Dependencies: ~ ~A compromised npm package could include code that reads files during development.~ 4. ~DNS Rebinding:~ (EDIT: This doesn't apply…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 2 · amended ·
Amended from ghsa record GHSA-g239-q96q-x4qm
- Revision 1 · created ·
Published from osv record GHSA-g239-q96q-x4qm
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2025-68155 Advisory: @vitejs/plugin-rsc has an Arbitrary File Read via `/__vite_rsc_findSourceMapURL` Endpoint IDs: CVE-2025-68155, GHSA-g239-q96q-x4qm Record: https://patchnext.com/advisories/cve-2025-68155 (revision 2, source checked 26 Oct 2026, 12:41 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: High (CVSS 7.5) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: @vitejs/plugin-rsc 0.5.8. A vendor fix does not mean a deployment is fixed. ## Affected components - npm @vitejs/plugin-rsc: affected < 0.5.8; fixed in 0.5.8 ## Suggested inspection (read-only) - `npm ls @vitejs/plugin-rsc --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on @vitejs/plugin-rsc. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://osv.dev/vulnerability/GHSA-g239-q96q-x4qm (OSV record GHSA-g239-q96q-x4qm lists affected ranges: npm @vitejs/plugin-rsc >=0 <0.5.8 (fixed)) - Verified: https://github.com/advisories/GHSA-g239-q96q-x4qm (GitHub-reviewed advisory GHSA-g239-q96q-x4qm lists affected ranges: npm @vitejs/plugin-rsc >=0 <0.5.8) Commands are suggestions: review each one before running it.
Loading voting…