GHSA-925w-6v3x-g4j4
MEDIUMSource Code Exposure Vulnerability in React Server Components
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Blast Radius
Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.
react-server-dom-parcelnpmreact-server-dom-turbopacknpmreact-server-dom-webpacknpmDescription
Impact
There is a source code exposure vulnerability in React Server Components.
React recommends updating immediately.
The vulnerability exists in versions 19.0.0, 19.0.1 19.1.0, 19.1.1, 19.1.2, 19.2.0 and 19.2.1 of:
These issues are present in the patches published last week.
Patches
Fixes were back ported to versions 19.0.2, 19.1.3, and 19.2.2.
If you are using any of the above packages please upgrade to any of the fixed versions immediately.
If your app’s React code does not use a server, your app is not affected by this vulnerability. If your app does not use a framework, bundler, or bundler plugin that supports React Server Components, your app is not affected by this vulnerability.
References
See the blog post for more information and upgrade instructions.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | react-server-dom-parcel | ≥ 19.0.0&&< 19.0.2 | 19.0.2 |
| 📦npm | react-server-dom-turbopack | ≥ 19.0.0&&< 19.0.2 | 19.0.2 |
| 📦npm | react-server-dom-webpack | ≥ 19.0.0&&< 19.0.2 | 19.0.2 |
| 📦npm | react-server-dom-parcel | ≥ 19.1.0&&< 19.1.3 | 19.1.3 |
| 📦npm | react-server-dom-parcel | ≥ 19.2.0&&< 19.2.2 | 19.2.2 |
| 📦npm | react-server-dom-turbopack | ≥ 19.1.0&&< 19.1.3 | 19.1.3 |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
williavs/nextjs-security-update
Batch upgrade all your Next.js apps to patched versions - fight back aga
kimtruth/CVE-2025-55183-poc
PoC for CVE-2025-55183
X-Cotang/CVE-2025-55183_POC
CVE-2025-55183 POC
StealthMoud/react-server-cve-lab
Security research lab for CVE-2025-55183 and CVE-2025-55184 in React Ser
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for react-server-dom-parcel. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update react-server-dom-parcel to 19.0.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-925w-6v3x-g4j4 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-925w-6v3x-g4j4 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-925w-6v3x-g4j4. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-925w-6v3x-g4j4 in your dependencies?
O3 detects GHSA-925w-6v3x-g4j4 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.