{"basis":"claimed","id":"CVE-2025-67779","name":"Meta react-server-dom-parcel","vendorProject":"Meta","product":"react-server-dom-parcel","publishedAt":"2025-12-11","cvss":{"score":7.5,"severity":"HIGH","version":"3.1"},"exploited":null,"epss":null,"coverage":{"cloudflare":{"status":"none","firstOn":null,"daysToRule":null},"aws":{"status":"none","firstOn":null,"daysToRule":null},"azure":{"status":"none","firstOn":null,"daysToRule":null},"google":{"status":"none","firstOn":null,"daysToRule":null},"fastly":{"status":"no_history","firstOn":null,"daysToRule":null},"vercel":{"status":"blocks","firstOn":"2025-12-11","daysToRule":0},"f5":{"status":"none","firstOn":null,"daysToRule":null},"akamai":{"status":"no_source","firstOn":null,"daysToRule":null},"crs":{"status":"none","firstOn":null,"daysToRule":null}},"title":null,"description":"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.","cwes":[],"vendors":[{"vendor":"cloudflare","status":"none","basis":"claimed","firstOn":null,"firstIsNew":false,"daysToRule":null,"daysAtMost":null,"freePlan":false,"claims":[]},{"vendor":"aws","status":"none","basis":"claimed","firstOn":null,"firstIsNew":false,"daysToRule":null,"daysAtMost":null,"freePlan":false,"claims":[]},{"vendor":"azure","status":"none","basis":"claimed","firstOn":null,"firstIsNew":false,"daysToRule":null,"daysAtMost":null,"freePlan":false,"claims":[]},{"vendor":"google","status":"none","basis":"claimed","firstOn":null,"firstIsNew":false,"daysToRule":null,"daysAtMost":null,"freePlan":false,"claims":[]},{"vendor":"fastly","status":"no_history","basis":"claimed","firstOn":null,"firstIsNew":false,"daysToRule":null,"daysAtMost":null,"freePlan":false,"claims":[]},{"vendor":"vercel","status":"blocks","basis":"claimed","firstOn":"2025-12-11","firstIsNew":true,"daysToRule":0,"daysAtMost":null,"freePlan":false,"claims":[{"id":"3c8eb50324272d403ff615a86101f799223cee52fa67528b67ea34b3d05d8985","cve_id":"CVE-2025-67779","vendor":"vercel","product":"Vercel WAF","rule_id":null,"rule_name":"React Server Components security update: DoS and Source Code Exposure","change":"new","default_action":"Block","published_on":"2025-12-11","source_url":"https://vercel.com/changelog/react-server-components-security-update-dos-and-source-code-exposure","source_title":"React Server Components security update: DoS and Source Code Exposure","excerpt":"We created new rules to address these vulnerabilities and deployed them to the Vercel WAF to automatically protect all projects hosted on Vercel at no cost.","first_seen_at":"2026-11-04T09:17:57.182Z"},{"id":"e9656a6b978b4c6dcaae5949f33979222a45a0cc4311eca3d7b79a557db720b7","cve_id":"CVE-2025-67779","vendor":"vercel","product":"Vercel WAF","rule_id":null,"rule_name":"Security Bulletin: CVE-2025-55184 and CVE-2025-55183","change":"new","default_action":"Block","published_on":"2025-12-11","source_url":"https://vercel.com/kb/bulletin/security-bulletin-cve-2025-55184-and-cve-2025-55183","source_title":"Security Bulletin: CVE-2025-55184 and CVE-2025-55183","excerpt":"We created new rules to address these vulnerabilities and deployed them to the Vercel WAF to automatically protect all projects hosted on Vercel at no cost.","first_seen_at":"2026-11-04T09:17:57.182Z"}]},{"vendor":"f5","status":"none","basis":"claimed","firstOn":null,"firstIsNew":false,"daysToRule":null,"daysAtMost":null,"freePlan":false,"claims":[]},{"vendor":"akamai","status":"no_source","basis":"claimed","firstOn":null,"firstIsNew":false,"daysToRule":null,"daysAtMost":null,"freePlan":false,"claims":[]},{"vendor":"crs","status":"none","basis":"claimed","firstOn":null,"firstIsNew":false,"daysToRule":null,"daysAtMost":null,"freePlan":false,"claims":[]}],"updatedAt":"2026-11-04T09:17:57.853Z","cvssVector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","ssvc":{"exploitation":"none","automatable":"yes","technicalImpact":"partial"},"kevAction":null,"kevNotes":null,"references":[{"url":"https://www.facebook.com/security/advisories/cve-2025-67779","name":null,"tags":["x_refsource_CONFIRM"]},{"url":"https://react.dev/blog/2025/12/11/denial-of-service-and-source-code-exposure-in-react-server-components","name":null,"tags":["x_refsource_CONFIRM"]}],"affected":[{"vendor":"Meta","product":"react-server-dom-parcel","affected":["19.0.2 through 19.0.2","19.1.3 through 19.1.3","19.2.2 through 19.2.2"],"fixed":[]},{"vendor":"Meta","product":"react-server-dom-turbopack","affected":["19.0.2 through 19.0.2","19.1.3 through 19.1.3","19.2.2 through 19.2.2"],"fixed":[]},{"vendor":"Meta","product":"react-server-dom-webpack","affected":["19.0.2 through 19.0.2","19.1.3 through 19.1.3","19.2.2 through 19.2.2"],"fixed":[]}],"briefing":{"status":{"id":"monitor","label":"Monitor"},"why":"It is reachable over the network without credentials or any user interaction (CVSS 7.5). Exploitation in the wild is not established by CISA KEV.","who":"Teams running Meta react-server-dom-parcel (19.0.2 through 19.0.2; 19.1.3 through 19.1.3; 19.2.2 through 19.2.2), Meta react-server-dom-turbopack (19.0.2 through 19.0.2; 19.1.3 through 19.1.3; 19.2.2 through 19.2.2) and Meta react-server-dom-webpack (19.0.2 through 19.0.2; 19.1.3 through 19.1.3; 19.2.2 through 19.2.2). Prioritise internet-facing instances.","what_to_do":[{"text":"Apply the vendor's fix; the advisory lists the affected and fixed versions."},{"text":"Keep a WAF rule in place while you patch: Vercel blocks it by default. A WAF rule reduces exposure; it does not replace the patch.","href":"#edge","linkText":"Edge coverage"},{"text":"Check which WAF sits in front of your site and whether it covers this CVE.","href":"#check","linkText":"Check your domain"}],"evidence":[{"heading":"CVE record","text":"CVSS 3.1 7.5 (high).","links":[{"label":"CVE-2025-67779","href":"https://www.cve.org/CVERecord?id=CVE-2025-67779"},{"label":"NVD","href":"https://nvd.nist.gov/vuln/detail/CVE-2025-67779"}]},{"heading":"Exploit evidence","text":"No public exploit code found in Exploit-DB, Metasploit, nuclei-templates or GitHub. That does not mean none exists.","links":[]},{"heading":"CISA KEV","text":"Not in the KEV catalog (catalog 2026.11.03, checked 2026-11-04). Absence from KEV is not evidence that it cannot be exploited.","links":[{"label":"CISA KEV catalog","href":"https://www.cisa.gov/known-exploited-vulnerabilities-catalog"}]},{"heading":"WAF vendor statements","text":"Vercel names it in a changelog. Quotes and dates below.","links":[{"label":"Vendor statements","href":"#evidence"}]}],"agent_prompt":"Assess whether the infrastructure available to you is affected by CVE-2025-67779 (Meta react-server-dom-parcel). Perform a read-only assessment within your authorized access. Do not send exploit traffic, scan third-party systems, change configuration or restart services.\n\n1. Verify the CVE record at https://www.cve.org/CVERecord?id=CVE-2025-67779 and the vendor advisory. Establish affected and fixed versions, including vendor backports. The record lists: Meta react-server-dom-parcel: affected 19.0.2 through 19.0.2; 19.1.3 through 19.1.3; 19.2.2 through 19.2.2 | Meta react-server-dom-turbopack: affected 19.0.2 through 19.0.2; 19.1.3 through 19.1.3; 19.2.2 through 19.2.2 | Meta react-server-dom-webpack: affected 19.0.2 through 19.0.2; 19.1.3 through 19.1.3; 19.2.2 through 19.2.2. Cite sources and retrieval dates; flag anything you cannot verify.\n2. Inventory deployments of Meta react-server-dom-parcel: asset, environment, owner where known, installed version or build, and how you confirmed it (package metadata, a version endpoint, image tags). An image tag alone does not prove the running version.\n3. Identify which deployments are reachable from the internet or untrusted networks, and through which paths (direct origin, load balancer, CDN or WAF).\n4. Assess compensating controls separately from patch status. Current edge WAF coverage for this CVE: Vercel: rule blocks by default. Live data: https://cve.vigilbase.com/api/v1/cves/CVE-2025-67779. Check whether the rule is enabled and in block mode on each path, and whether any path bypasses the WAF. A WAF rule is not a patch.\n5. Check logs on exposed instances for requests matching the public exploit, if your access allows.\n\nReturn a short summary and a table: asset | version/build | assessment (affected, fixed, not applicable, unknown) | exposure | compensating control | evidence | next action. List what you could not assess and the access needed to resolve it. Do not infer absence of compromise from patch status or a lack of alerts.\n\nRemediation guidance: Apply the vendor's fix; the advisory lists the affected and fixed versions. Keep a WAF rule in place while you patch: Vercel blocks it by default. A WAF rule reduces exposure; it does not replace the patch.\nMore: https://cve.vigilbase.com/cve/CVE-2025-67779"},"measured":[],"sightings":null,"social":{"total":0,"first_seen":null,"daily":[{"day":"2026-10-22","posts":0},{"day":"2026-10-23","posts":0},{"day":"2026-10-24","posts":0},{"day":"2026-10-25","posts":0},{"day":"2026-10-26","posts":0},{"day":"2026-10-27","posts":0},{"day":"2026-10-28","posts":0},{"day":"2026-10-29","posts":0},{"day":"2026-10-30","posts":0},{"day":"2026-10-31","posts":0},{"day":"2026-11-01","posts":0},{"day":"2026-11-02","posts":0},{"day":"2026-11-03","posts":0},{"day":"2026-11-04","posts":0}],"top_posts":[],"exploit_repositories":[]}}