CVE-2025-67779
HIGHDenial of Service 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-parcelnpmDescription
It was found that the fix addressing CVE-2025-55184 in React Server Components was incomplete and does not prevent a denial of service attack in a specific case. React Server Components versions 19.0.2, 19.1.3 and 19.2.2 are affected, allowing unsafe deserialization of payloads from HTTP requests to Server Function endpoints. This can cause an infinite loop that hangs the server process and may prevent future HTTP requests from being served.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | react-server-dom-parcel | ≥ 19.0.2&&< 19.0.3 | 19.0.3 |
| 📦npm | react-server-dom-parcel | ≥ 19.1.3&&< 19.1.4 | 19.1.4 |
| 📦npm | react-server-dom-parcel | ≥ 19.2.2&&< 19.2.3 | 19.2.3 |
| 📦npm | react-server-dom-turbopack | ≥ 19.0.2&&< 19.0.3 | 19.0.3 |
| 📦npm | react-server-dom-turbopack | ≥ 19.1.3&&< 19.1.4 | 19.1.4 |
| 📦npm | react-server-dom-turbopack | ≥ 19.2.2&&< 19.2.3 | 19.2.3 |
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.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-67779 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 CVE-2025-67779 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 CVE-2025-67779. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2025-67779 in your dependencies?
O3 detects CVE-2025-67779 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.