CVE-2025-67779 — Deserialization of Untrusted Data in Facebook React
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 20% (30-day exploitation probability)+15
- Technical severity (high)+6
- Automatable exploitation (SSVC)+3
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Facebook React, Meta React-server-dom-parcel, Meta React-server-dom-turbopack…).
- The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- EPSS ahead of 97% of scored CVEs: prioritize it in the patch queue.
- Search available logs for exploit probes matching the vulnerability class (insecure deserialization), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| React | version 19.0.2version 19.1.3version 19.2.2 | Vulnerable | NIST National Vulnerability Database | |
| Meta | React-server-dom-parcel | ≥ 19.0.2 and ≤ 19.0.2≥ 19.1.3 and ≤ 19.1.3≥ 19.2.2 and ≤ 19.2.2 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Meta | React-server-dom-turbopack | ≥ 19.0.2 and ≤ 19.0.2≥ 19.1.3 and ≤ 19.1.3≥ 19.2.2 and ≤ 19.2.2 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Meta | React-server-dom-webpack | ≥ 19.0.2 and ≤ 19.0.2≥ 19.1.3 and ≤ 19.1.3≥ 19.2.2 and ≤ 19.2.2 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Vercel | Next.js |
≥ 13.3.0 and < 14.2.35≥ 15.0.0 and < 15.0.7≥ 15.1.0 and < 15.1.11≥ 15.2.0 and < 15.2.8≥ 15.3.0 and < 15.3.8≥ 15.4.0 and < 15.4.10≥ 15.5.0 and < 15.5.9≥ 16.0.0 and < 16.0.10 and 81 moreversion 15.6.0version 15.6.0-canary0version 15.6.0-canary1version 15.6.0-canary10version 15.6.0-canary11version 15.6.0-canary12version 15.6.0-canary13version 15.6.0-canary14version 15.6.0-canary15version 15.6.0-canary16version 15.6.0-canary17version 15.6.0-canary18version 15.6.0-canary19version 15.6.0-canary2version 15.6.0-canary20version 15.6.0-canary21version 15.6.0-canary22version 15.6.0-canary23version 15.6.0-canary24version 15.6.0-canary25version 15.6.0-canary26version 15.6.0-canary27version 15.6.0-canary28version 15.6.0-canary29version 15.6.0-canary3version 15.6.0-canary30version 15.6.0-canary31version 15.6.0-canary32version 15.6.0-canary33version 15.6.0-canary34version 15.6.0-canary35version 15.6.0-canary36version 15.6.0-canary37version 15.6.0-canary38version 15.6.0-canary39version 15.6.0-canary4version 15.6.0-canary40version 15.6.0-canary41version 15.6.0-canary42version 15.6.0-canary43version 15.6.0-canary44version 15.6.0-canary45version 15.6.0-canary46version 15.6.0-canary47version 15.6.0-canary48version 15.6.0-canary49version 15.6.0-canary5version 15.6.0-canary50version 15.6.0-canary51version 15.6.0-canary52version 15.6.0-canary53version 15.6.0-canary54version 15.6.0-canary55version 15.6.0-canary56version 15.6.0-canary57version 15.6.0-canary58version 15.6.0-canary59version 15.6.0-canary6version 15.6.0-canary7version 15.6.0-canary8version 15.6.0-canary9version 16.1.0version 16.1.0-canary0version 16.1.0-canary1version 16.1.0-canary10version 16.1.0-canary11version 16.1.0-canary12version 16.1.0-canary13version 16.1.0-canary14version 16.1.0-canary15version 16.1.0-canary16version 16.1.0-canary17version 16.1.0-canary18version 16.1.0-canary2version 16.1.0-canary3version 16.1.0-canary4version 16.1.0-canary5version 16.1.0-canary6version 16.1.0-canary7version 16.1.0-canary8version 16.1.0-canary9 |
Vulnerable | NIST National Vulnerability Database |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 7.5 | CVSS 3.1 | High | 3.9 | 3.6 | cve-assign@fb.com via NIST National Vulnerability Database |
| 7.5 | CVSS 3.1 | High | — | — | Meta via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H (score shown at the top: cve-assign@fb.com) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
EPSS over time FIRST
Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 19.99%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
- Monitor serialized objects in requests and unexpected processes spawned by the runtime.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · meta/react-server-dom-parcel, meta/react-server-dom-turbopack, meta/react-server-dom-webpack
- SSVC assessment updated
- Record published
- CVSS changed · 7.5
- Source status changed · → Modified
- Record created in this database
- 2025
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
2 on the record
Elsewhere on this site
Related CVEs (same products)
- Medium CVE-2026-94543 Next.js: Cache poisoning of SSG and ISR pages in self-hosted Next.js applications 13d
- Medium CVE-2026-94483 Next.js: Server-Side Request Forgery in Image Optimization 13d
- Low CVE-2026-44582 Next.js: Cache poisoning via collisions in React Server Component cache-busting May 13, 2026
- High CVE-2026-45109 Next.js: Middleware / Proxy bypass in App Router applications via segment-prefetch routes May 13, 2026
- Medium CVE-2026-44580 Next.js: Cross-site scripting in beforeInteractive scripts with untrusted input May 13, 2026
- Medium CVE-2026-44581 Next.js: Cross-site scripting in App Router applications using CSP nonces May 13, 2026
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No fixed version, patch or mitigation documented.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2025-67779 is "Deserialization of Untrusted Data in Facebook React", rated High. It affects React (Facebook); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.5 describes technical severity. EPSS 19.99% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.