CVE-2025-67779CWE-400CWE-502denial-of-serviceinsecure-deserialization

CVE-2025-67779

High Β· published December 12, 2025

CVSS v3.1
7.5
EPSS
20%
Percentile
97.4
In the wild
Unconfirmed
What it is

⚑ An unfinished fix has left React Server Components vulnerable to denial of service in specific scenarios! 🚨 Think of it like a restaurant that received a complaint about their slow service. They removed a few menu items but forgot to address the crowding problem β€” now, the kitchen gets overwhelmed and can’t serve any more orders. This vulnerability allows payloads from HTTP requests to cause a loop that can freeze server processes! An attacker could exploit this flaw to send malformed payloads, triggering an infinite loop that effectively hangs the server. This results in users being unable to access the service, leading to downtime and frustrated customers β€” absolutely devastating for any application relying on quick responsiveness!

Put simply

Think of it like a restaurant that received a complaint about their slow service. They removed a few menu items but forgot to address the crowding problem β€” now, the kitchen gets overwhelmed and can’t serve any more orders. This vulnerability allows payloads from HTTP requests to cause a loop that can freeze server processes! This vulnerability allows unsafe deserialization of payloads from HTTP requests to React Server Function endpoints, leading to denial of service as the server enters an infinite processing loop. Affected versions include 19.0.2, 19.1.3, and 19.2.2, which failed to fully address a previous issue identified in CVE-2025-55184.

What to do

An attacker could exploit this flaw to send malformed payloads, triggering an infinite loop that effectively hangs the server. This results in users being unable to access the service, leading to downtime and frustrated customers β€” absolutely devastating for any application relying on quick responsiveness! To mitigate this risk, immediately upgrade React Server Components to a fixed version that addresses this vulnerability. Additionally, implement request validation to ensure harmful payloads are rejected before being processed. Regularly monitor for updates and security advisories to stay ahead! You've got this! Follow these steps, and you'll keep your application running smoothly and securely! πŸ›‘οΈ

The record
Technical detail
CVSS v3.1
7.5 Β· HIGH
Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
CVSS v4.0
Not supplied
EPSS
0.19986 Β· 97.4th percentile
Weaknesses
CWE-400 Β· Uncontrolled Resource Consumption; CWE-502 Β· Deserialization of Untrusted Data
Published
2025-12-12T05:15Z
Affected products (92)
ProductVersionsFixed in
facebook/reactall versionsβ€”
facebook/reactall versionsβ€”
facebook/reactall versionsβ€”
vercel/next.jsβ‰₯ 13.3.0, < 14.2.3514.2.35
vercel/next.jsβ‰₯ 15.0.0, < 15.0.715.0.7
vercel/next.jsβ‰₯ 15.1.0, < 15.1.1115.1.11
vercel/next.jsβ‰₯ 15.2.0, < 15.2.815.2.8
vercel/next.jsβ‰₯ 15.3.0, < 15.3.815.3.8
vercel/next.jsβ‰₯ 15.4.0, < 15.4.1015.4.10
vercel/next.jsβ‰₯ 15.5.0, < 15.5.915.5.9
vercel/next.jsβ‰₯ 16.0.0, < 16.0.1016.0.10
vercel/next.jsall versionsβ€”
vercel/next.jsall versionsβ€”
vercel/next.jsall versionsβ€”
vercel/next.jsall versionsβ€”
vercel/next.jsall versionsβ€”
vercel/next.jsall versionsβ€”
vercel/next.jsall versionsβ€”
vercel/next.jsall versionsβ€”
vercel/next.jsall versionsβ€”
vercel/next.jsall versionsβ€”
vercel/next.jsall versionsβ€”
vercel/next.jsall versionsβ€”
vercel/next.jsall versionsβ€”
vercel/next.jsall versionsβ€”
vercel/next.jsall versionsβ€”
vercel/next.jsall versionsβ€”
vercel/next.jsall versionsβ€”
vercel/next.jsall versionsβ€”
vercel/next.jsall versionsβ€”
vercel/next.jsall versionsβ€”
vercel/next.jsall versionsβ€”
vercel/next.jsall versionsβ€”
vercel/next.jsall versionsβ€”
vercel/next.jsall versionsβ€”
vercel/next.jsall versionsβ€”
vercel/next.jsall versionsβ€”
vercel/next.jsall versionsβ€”
vercel/next.jsall versionsβ€”
vercel/next.jsall versionsβ€”
vercel/next.jsall versionsβ€”
vercel/next.jsall versionsβ€”
vercel/next.jsall versionsβ€”
vercel/next.jsall versionsβ€”
vercel/next.jsall versionsβ€”
vercel/next.jsall versionsβ€”
vercel/next.jsall versionsβ€”
vercel/next.jsall versionsβ€”
vercel/next.jsall versionsβ€”
vercel/next.jsall versionsβ€”
vercel/next.jsall versionsβ€”
vercel/next.jsall versionsβ€”
vercel/next.jsall versionsβ€”
vercel/next.jsall versionsβ€”
vercel/next.jsall versionsβ€”
vercel/next.jsall versionsβ€”
vercel/next.jsall versionsβ€”
vercel/next.jsall versionsβ€”
vercel/next.jsall versionsβ€”
vercel/next.jsall versionsβ€”
vercel/next.jsall versionsβ€”
vercel/next.jsall versionsβ€”
vercel/next.jsall versionsβ€”
vercel/next.jsall versionsβ€”
vercel/next.jsall versionsβ€”
vercel/next.jsall versionsβ€”
vercel/next.jsall versionsβ€”
vercel/next.jsall versionsβ€”
vercel/next.jsall versionsβ€”
vercel/next.jsall versionsβ€”
vercel/next.jsall versionsβ€”
vercel/next.jsall versionsβ€”
vercel/next.jsall versionsβ€”
vercel/next.jsall versionsβ€”
vercel/next.jsall versionsβ€”
vercel/next.jsall versionsβ€”
vercel/next.jsall versionsβ€”
vercel/next.jsall versionsβ€”
vercel/next.jsall versionsβ€”
vercel/next.jsall versionsβ€”
vercel/next.jsall versionsβ€”
vercel/next.jsall versionsβ€”
vercel/next.jsall versionsβ€”
vercel/next.jsall versionsβ€”
vercel/next.jsall versionsβ€”
vercel/next.jsall versionsβ€”
vercel/next.jsall versionsβ€”
vercel/next.jsall versionsβ€”
vercel/next.jsall versionsβ€”
vercel/next.jsall versionsβ€”
vercel/next.jsall versionsβ€”
vercel/next.jsall versionsβ€”
References (2)
EPSS history
Timeline
  • 11 DEC 23:36Z
    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…
    cvelistv5