CVE-2025-67779: React Server Components Denial of Service via Incomplete Deserialization Fix
- Vendors
- VercelMeta Platforms
CVE-2025-67779 is a denial-of-service vulnerability caused by an incomplete fix for CVE-2025-55184 in React Server Components. It affects react-server-dom-webpack, react-server-dom-parcel, and react-server-dom-turbopack versions 19.0.2, 19.1.3, and 19.2.2. A specially crafted HTTP request processed by the Server Function deserialization logic can trigger an infinite loop, consuming CPU resources and hanging the server process. The vulnerability is remotely exploitable without authentication and has a CVSS score of 7.5. It is distinct from the React2Shell remote code execution vulnerability.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Successful exploitation can cause sustained CPU consumption and render the affected server process unresponsive, potentially preventing subsequent HTTP requests from being served. Applications sharing that process may consequently become unavailable. This vulnerability does not itself provide remote code execution or source code disclosure.
Mitigation
If you can’t patch tonight, do this now.
WAF rules targeting malicious React Server Components requests can provide interim protection; Vercel deployed such rules for hosted projects. These rules filter known exploit patterns but cannot guarantee protection against every variant and are not a substitute for upgrading. Restrict access to preview and non-production deployments and audit shareable deployment links. No complete workaround other than upgrading is identified.
Remediation
Patch, then assume compromise.
Upgrade affected react-server-dom-webpack, react-server-dom-parcel, and react-server-dom-turbopack packages to 19.0.3, 19.1.4, or 19.2.3, respectively, or a later supported patched release. Applications that installed the initial CVE-2025-55184 fixes must upgrade again. For affected Next.js applications, the corresponding fixed releases are 14.2.35, 15.0.7, 15.1.11, 15.2.8, 15.3.8, 15.4.10, 15.5.9, and 16.0.10; fixed canary releases are 15.6.0-canary.60 and 16.1.0-canary.19. Update and redeploy all affected production, preview, and older accessible deployments.
Exploits
No validated public exploits yet. Hidden: 5 rejected by Mallory's analysis as not a working exploit.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
References
Frequently asked questions
- Is CVE-2025-67779 exploited in the wild?
- As of Oct 30, 2026, Mallory has no reports of CVE-2025-67779 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2025-67779?
- As of Oct 30, 2026, Mallory has found no public exploit for CVE-2025-67779.
- Is there a patch for CVE-2025-67779?
- Upgrade affected react-server-dom-webpack, react-server-dom-parcel, and react-server-dom-turbopack packages to 19.0.3, 19.1.4, or 19.2.3, respectively, or a later supported patched release. Applications that installed the initial CVE-2025-55184 fixes must upgrade again.
- What products are affected by CVE-2025-67779?
- Meta Platforms React and Vercel Next.Js.
- How severe is CVE-2025-67779?
- CVE-2025-67779 has a CVSS v3.1 score of 7.5 (High) and an EPSS score of 15.5% (97th percentile) as of Oct 30, 2026.
Recent activity
52 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.