CVE-2025-67779 — react-server-dom-parcel
HIGHCVE-2025-67779 is a high-severity (CVSS 7.5) Deserialization of Untrusted Data vulnerability in react-server-dom-parcel. EPSS puts its 30-day exploitation probability at 20.0% (97th percentile). A fix is available for react-server-dom-parcel — see the affected versions and patch details below.
Denial of Service Vulnerability in React Server Components
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2025-67779.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
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.
react-server-dom-parcelnpmDescription
Impact
It was found that the fix to address CVE-2025-55184 in React Server Components was incomplete and does not prevent a denial of service attack in a specific case.
We recommend updating immediately.
The vulnerability exists in versions 19.0.2, 19.1.3, and 19.2.2 of:
These issues are present in the patches published on December 11th, 2025.
Patches
Fixes were back ported to versions 19.0.3, 19.1.4, and 19.2.3.
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.2&&< 19.0.3 | 19.0.3npm install react-server-dom-parcel@19.0.3 |
| 📦npm | react-server-dom-parcel | ≥ 19.1.3&&< 19.1.4 | 19.1.4npm install react-server-dom-parcel@19.1.4 |
| 📦npm | react-server-dom-parcel | ≥ 19.2.2&&< 19.2.3 | 19.2.3npm install react-server-dom-parcel@19.2.3 |
| 📦npm | react-server-dom-turbopack | ≥ 19.0.2&&< 19.0.3 | 19.0.3npm install react-server-dom-turbopack@19.0.3 |
| 📦npm | react-server-dom-turbopack | ≥ 19.1.3&&< 19.1.4 | 19.1.4npm install react-server-dom-turbopack@19.1.4 |
| 📦npm | react-server-dom-turbopack | ≥ 19.2.2&&< 19.2.3 | 19.2.3npm install react-server-dom-turbopack@19.2.3 |
Affected Products
reactfacebooknext.jsvercelDetection & 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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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
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 CVE-2025-67779 in your dependencies?
Find it across npm, including transitive dependencies.