React Server Components are Vulnerable to RCEGHSA-fmh4-wr37-44fp
CRITICALGHSA-fmh4-wr37-44fp is a critical-severity (CVSS 10) remote code execution vulnerability in @vitejs/plugin-rsc. A fix is available for @vitejs/plugin-rsc — see the affected versions and patch details below.
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
@vitejs/plugin-rscnpmDescription
Summary
@vitejs/plugin-rsc vendors react-server-dom-webpack, which contained an unauthenticated remote code execution vulnerability in versions prior to 19.0.1, 19.1.2, and 19.2.1. See details in React repository's advisory https://github.com/facebook/react/security/advisories/GHSA-fv66-9v8q-g76r
Impact
Applications using affected versions of @vitejs/plugin-rsc are vulnerable to unauthenticated remote code execution through deserialization of untrusted data. An attacker can execute arbitrary code remotely without authentication, affecting confidentiality, integrity, and availability.
Recommendations
Upgrade immediately to @vitejs/[email protected] or later.
Workarounds
Applications not using server-side React or React Server Components are unaffected.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @vitejs/plugin-rsc | all versions | 0.5.3npm install @vitejs/plugin-rsc@0.5.3 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @vitejs/plugin-rsc, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @vitejs/plugin-rsc to 0.5.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-fmh4-wr37-44fp is resolved across your whole dependency graph.
Workarounds
Do not deserialise data from untrusted sources: where the format allows it, restrict deserialisation to an explicit allowlist of expected types, and prefer a data-only format (JSON, Protobuf) over one that can reconstruct arbitrary objects until you can upgrade.
Frequently Asked Questions
Is GHSA-fmh4-wr37-44fp in your dependencies?
Find it across npm, including transitive dependencies.