1. Home
  2. Vulnerabilities
  3. CVE-2025-67779
7.5
HIGH CVSS 3.1
CVE-2025-67779
"React Server Components Denial of Service Vulnerability"
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.

INFO

Published Date :

Dec. 12, 2025, 12:15 a.m.

Last Modified :

Dec. 12, 2025, 7:16 p.m.

Remotely Exploit :

No

Source :

[email protected]
Affected Products

The following products are affected by CVE-2025-67779 vulnerability. Even if cvefeed.io is aware of the exact versions of the products that are affected, the information is not represented in the table below.

ID Vendor Product Action
1 Vercel next.js
1 Facebook react
: Total Affected Vendor : 2 | Products : 2
CVSS Scores
The Common Vulnerability Scoring System is a standardized framework for assessing the severity of vulnerabilities in software and systems. We collect and displays CVSS scores from various sources for each CVE.
Score Version Severity Vector Exploitability Score Impact Score Source
CVSS 3.1 HIGH 4fc57720-52fe-4431-a0fb-3d2c8747b827
CVSS 3.1 HIGH [email protected]
CVSS 3.1 HIGH MITRE-CVE
Solution
Update React Server Components to the latest version to fix an incomplete denial of service vulnerability.
  • Update React Server Components to a non-vulnerable version.
  • Apply the vendor-provided patch for CVE-2025-55184.
  • Verify the denial of service vulnerability is mitigated.
Public PoC/Exploit Available at Github

CVE-2025-67779 has a 18 public PoC/Exploit available at Github. Go to the Public Exploits tab to see the list.

References to Advisories, Solutions, and Tools

Here, you will find a curated list of external links that provide in-depth information, practical solutions, and valuable tools related to CVE-2025-67779.

URL Resource
https://react.dev/blog/2025/12/11/denial-of-service-and-source-code-exposure-in-react-server-components Vendor Advisory
https://www.facebook.com/security/advisories/cve-2025-67779 Vendor Advisory
CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorizes the common flaws or weaknesses that can lead to vulnerabilities. CVE-2025-67779 is associated with the following CWEs:

Common Attack Pattern Enumeration and Classification (CAPEC)

Common Attack Pattern Enumeration and Classification (CAPEC) stores attack patterns, which are descriptions of the common attributes and approaches employed by adversaries to exploit the CVE-2025-67779 weaknesses.

We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).

Profile Photo
DanielWarg/Reflektera

None

JavaScript TypeScript CSS PLpgSQL

Updated: 4 days, 12 hours ago
0 stars 0 fork 0 watcher
Born at : Dec. 16, 2025, 5:53 p.m. This repo has been linked 3 different CVEs too.
Profile Photo
pnndrs/react-rsc-cve-scanner

behavior based cve detection for react server components

application-security appsec cve internal-tooling nextjs react react-security react-server-components rsc security-research security-tooling turbopack vulnerability-scanners

Python

Updated: 3 days, 5 hours ago
0 stars 0 fork 0 watcher
Born at : Dec. 15, 2025, 5:48 p.m. This repo has been linked 4 different CVEs too.
Profile Photo
pjt3591oo/2025-55184_2025-55183-_poc

None

Shell TypeScript JavaScript

Updated: 6 days, 16 hours ago
0 stars 0 fork 0 watcher
Born at : Dec. 15, 2025, 10:50 a.m. This repo has been linked 3 different CVEs too.
Profile Photo
abdozkaya/rsc-security-auditor

🛡️ Audit your Next.js & React Server Components stack for critical vulnerabilities (CVE-2025-66478, CVE-2025-55184). Detects risks & generates fix commands. 100% Client-side.

cve-scanning nextjs react rsc vulnerability-scanners

CSS TypeScript JavaScript

Updated: 1 week ago
4 stars 0 fork 0 watcher
Born at : Dec. 12, 2025, 10:37 p.m. This repo has been linked 4 different CVEs too.
Profile Photo
asg5704/check-cve

A collection of Bash scripts that check CVEs relating to Frontend

Shell

Updated: 1 week, 2 days ago
0 stars 0 fork 0 watcher
Born at : Dec. 12, 2025, 4:43 p.m. This repo has been linked 5 different CVEs too.
Profile Photo
1imn1/rsc-exposure-audit

Black-box exposure audit for Next.js / React Server Components (RSC) endpoints (non-exploit).

Python

Updated: 4 days, 10 hours ago
1 stars 0 fork 0 watcher
Born at : Dec. 12, 2025, 2:58 p.m. This repo has been linked 4 different CVEs too.
Profile Photo
williavs/nextjs-security-update

Batch upgrade all your Next.js apps to patched versions - fight back against CVE-2025-55183/55184/67779

Shell

Updated: 1 week ago
8 stars 0 fork 0 watcher
Born at : Dec. 12, 2025, 4:17 a.m. This repo has been linked 4 different CVEs too.
Profile Photo
keytech-ec/transporte-platform

None

TypeScript JavaScript CSS

Updated: 3 days, 7 hours ago
0 stars 0 fork 0 watcher
Born at : Dec. 10, 2025, 10:18 p.m. This repo has been linked 3 different CVEs too.
Profile Photo
theori-io/reactguard

ReactGuard provides framework- and vulnerability-detection tooling for CVE-2025-55182 (React2Shell)

cve-2025-55182 nextjs react react2shell waku reactguard cve-2025-55183 cve-2025-55184 cve-2025-67779

Python Makefile

Updated: 4 days, 10 hours ago
16 stars 1 fork 1 watcher
Born at : Dec. 10, 2025, 4:49 a.m. This repo has been linked 4 different CVEs too.
Profile Photo
sean-nicholas/vuln-dependency-upgrader

None

JavaScript TypeScript CSS

Updated: 1 week ago
0 stars 0 fork 0 watcher
Born at : Dec. 4, 2025, 6:44 a.m. This repo has been linked 3 different CVEs too.
Profile Photo
anaknegeri/neurox

None

Dockerfile JavaScript TypeScript CSS

Updated: 3 days, 1 hour ago
0 stars 0 fork 0 watcher
Born at : Dec. 2, 2025, 7:46 a.m. This repo has been linked 4 different CVEs too.
Profile Photo
chrisph124/nfd-blog

None

JavaScript TypeScript CSS

Updated: 6 days, 14 hours ago
0 stars 0 fork 0 watcher
Born at : Nov. 15, 2025, 4:28 p.m. This repo has been linked 3 different CVEs too.
Profile Photo
douglasgoodwin/memories-observations

Code to build the site https://sounds.cairn.com

TypeScript JavaScript CSS DIGITAL Command Language

Updated: 1 week ago
0 stars 0 fork 0 watcher
Born at : Nov. 8, 2025, 1:46 a.m. This repo has been linked 4 different CVEs too.
Profile Photo
lance0/latch

Latch is a lightweight, security-minded authentication library for Next.js that implements OpenID Connect the right way — PKCE, refresh tokens, cookie sealing — and works in Azure Government clouds out of the box.

authentication azure gcc-high nextjs oidc react sovereign-cloud

TypeScript CSS JavaScript

Updated: 5 days, 14 hours ago
1 stars 0 fork 0 watcher
Born at : Oct. 21, 2025, 7:08 p.m. This repo has been linked 2 different CVEs too.
Profile Photo
Sadeeq499/sadeeq-portfolio

None

CSS JavaScript

Updated: 1 week, 2 days ago
0 stars 0 fork 0 watcher
Born at : Oct. 14, 2025, 6:55 p.m. This repo has been linked 4 different CVEs too.

Results are limited to the first 15 repositories due to potential performance issues.

The following list is the news that have been mention CVE-2025-67779 vulnerability anywhere in the article.

  • CybersecurityNews
OpenAI GPT-5.2-Codex Supercharges Agentic Coding and Vulnerability Detection

OpenAI has unveiled GPT-5.2-Codex, a cutting-edge model optimized for agentic coding and enhanced cybersecurity tasks. The release highlights breakthroughs in handling complex software engineering and ... Read more

Published Date: Dec 19, 2025 (3 days, 1 hour ago)
  • The Register
China, Iran are having a field day with React2Shell, Google warns

At least five more Chinese spy crews, Iran-linked goons, and financially motivated criminals are now attacking the React2Shell, a maximum-severity flaw in the widely used React JavaScript library, acc ... Read more

Published Date: Dec 15, 2025 (6 days, 10 hours ago)
  • The Register
New React vulns leak secrets, invite DoS attacks

If you're running React Server Components, you just can't catch a break. In addition to already-reported flaws, newly discovered bugs allow attackers to hang vulnerable servers and potentially leak Se ... Read more

Published Date: Dec 12, 2025 (1 week, 2 days ago)
  • Google Cloud
Multiple Threat Actors Exploit React2Shell (CVE-2025-55182)

Written by: Aragorn Tseng, Robert Weiner, Casey Charrier, Zander Work, Genevieve Stark, Austin Larsen Introduction On Dec. 3, 2025, a critical unauthenticated remote code execution (RCE) vulnerability ... Read more

Published Date: Dec 12, 2025 (1 week, 2 days ago)
  • security.nl
Nieuwe React-kwetsbaarheden leiden tot denial of service en broncode-lek

Onderzoekers hebben nieuwe kwetsbaarheden in React Server Components ontdekt waardoor aanvallers een denial of service kunnen veroorzaken of broncode stelen. Er zijn updates beschikbaar gesteld en Rea ... Read more

Published Date: Dec 12, 2025 (1 week, 2 days ago)
  • The Hacker News
New React RSC Vulnerabilities Enable DoS and Source Code Exposure

Dec 12, 2025Ravie LakshmananSoftware Security / Vulnerability The React team has released fixes for two new types of flaws in React Server Components (RSC) that, if successfully exploited, could res ... Read more

Published Date: Dec 12, 2025 (1 week, 2 days ago)
  • Daily CyberSecurity
React Patches Two New Flaws Risking Server-Crashing DoS and Source Code Disclosure

The security saga surrounding React Server Components continues this week. Just days after the React team patched a critical remote code execution (RCE) flaw, security researchers digging into those v ... Read more

Published Date: Dec 12, 2025 (1 week, 3 days ago)
  • CybersecurityNews
New Vulnerabilities in React Server Components Allow DoS Attacks and Source Code Leaks

Less than a week after addressing a critical Remote Code Execution (RCE) vulnerability, the React team has disclosed three additional security flaws affecting React Server Components (RSC). Security r ... Read more

Published Date: Dec 12, 2025 (1 week, 3 days ago)

Results are limited to the first 20 news articles due to potential performance issues.

The following table lists the changes that have been made to the CVE-2025-67779 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.

  • CVE Modified by 134c704f-9b21-4f2e-91b3-4a467353bcc0

    Dec. 12, 2025

    Action Type Old Value New Value
    Added CWE CWE-400
    Added CWE CWE-502
  • Initial Analysis by [email protected]

    Dec. 12, 2025

    Action Type Old Value New Value
    Added CWE CWE-502
    Added CPE Configuration OR *cpe:2.3:a:facebook:react:19.2.2:*:*:*:*:*:*:* *cpe:2.3:a:facebook:react:19.0.2:*:*:*:*:*:*:* *cpe:2.3:a:facebook:react:19.1.3:*:*:*:*:*:*:*
    Added CPE Configuration OR *cpe:2.3:a:vercel:next.js:15.6.0:-:*:*:*:node.js:*:* *cpe:2.3:a:vercel:next.js:15.6.0:canary0:*:*:*:node.js:*:* *cpe:2.3:a:vercel:next.js:15.6.0:canary1:*:*:*:node.js:*:* *cpe:2.3:a:vercel:next.js:15.6.0:canary10:*:*:*:node.js:*:* *cpe:2.3:a:vercel:next.js:15.6.0:canary11:*:*:*:node.js:*:* *cpe:2.3:a:vercel:next.js:15.6.0:canary12:*:*:*:node.js:*:* *cpe:2.3:a:vercel:next.js:15.6.0:canary13:*:*:*:node.js:*:* *cpe:2.3:a:vercel:next.js:15.6.0:canary14:*:*:*:node.js:*:* *cpe:2.3:a:vercel:next.js:15.6.0:canary15:*:*:*:node.js:*:* *cpe:2.3:a:vercel:next.js:15.6.0:canary16:*:*:*:node.js:*:* *cpe:2.3:a:vercel:next.js:15.6.0:canary17:*:*:*:node.js:*:* *cpe:2.3:a:vercel:next.js:15.6.0:canary18:*:*:*:node.js:*:* *cpe:2.3:a:vercel:next.js:15.6.0:canary19:*:*:*:node.js:*:* *cpe:2.3:a:vercel:next.js:15.6.0:canary2:*:*:*:node.js:*:* *cpe:2.3:a:vercel:next.js:15.6.0:canary20:*:*:*:node.js:*:* *cpe:2.3:a:vercel:next.js:15.6.0:canary21:*:*:*:node.js:*:* *cpe:2.3:a:vercel:next.js:15.6.0:canary22:*:*:*:node.js:*:* *cpe:2.3:a:vercel:next.js:15.6.0:canary23:*:*:*:node.js:*:* *cpe:2.3:a:vercel:next.js:15.6.0:canary24:*:*:*:node.js:*:* *cpe:2.3:a:vercel:next.js:15.6.0:canary25:*:*:*:node.js:*:* *cpe:2.3:a:vercel:next.js:15.6.0:canary26:*:*:*:node.js:*:* *cpe:2.3:a:vercel:next.js:15.6.0:canary27:*:*:*:node.js:*:* *cpe:2.3:a:vercel:next.js:15.6.0:canary28:*:*:*:node.js:*:* *cpe:2.3:a:vercel:next.js:15.6.0:canary29:*:*:*:node.js:*:* *cpe:2.3:a:vercel:next.js:15.6.0:canary3:*:*:*:node.js:*:* *cpe:2.3:a:vercel:next.js:15.6.0:canary30:*:*:*:node.js:*:* *cpe:2.3:a:vercel:next.js:15.6.0:canary31:*:*:*:node.js:*:* *cpe:2.3:a:vercel:next.js:15.6.0:canary32:*:*:*:node.js:*:* *cpe:2.3:a:vercel:next.js:15.6.0:canary33:*:*:*:node.js:*:* *cpe:2.3:a:vercel:next.js:15.6.0:canary34:*:*:*:node.js:*:* *cpe:2.3:a:vercel:next.js:15.6.0:canary35:*:*:*:node.js:*:* *cpe:2.3:a:vercel:next.js:15.6.0:canary36:*:*:*:node.js:*:* *cpe:2.3:a:vercel:next.js:15.6.0:canary37:*:*:*:node.js:*:* *cpe:2.3:a:vercel:next.js:15.6.0:canary38:*:*:*:node.js:*:* *cpe:2.3:a:vercel:next.js:15.6.0:canary39:*:*:*:node.js:*:* *cpe:2.3:a:vercel:next.js:15.6.0:canary4:*:*:*:node.js:*:* *cpe:2.3:a:vercel:next.js:15.6.0:canary40:*:*:*:node.js:*:* *cpe:2.3:a:vercel:next.js:15.6.0:canary41:*:*:*:node.js:*:* *cpe:2.3:a:vercel:next.js:15.6.0:canary42:*:*:*:node.js:*:* *cpe:2.3:a:vercel:next.js:15.6.0:canary43:*:*:*:node.js:*:* *cpe:2.3:a:vercel:next.js:15.6.0:canary44:*:*:*:node.js:*:* *cpe:2.3:a:vercel:next.js:15.6.0:canary45:*:*:*:node.js:*:* *cpe:2.3:a:vercel:next.js:15.6.0:canary46:*:*:*:node.js:*:* *cpe:2.3:a:vercel:next.js:15.6.0:canary47:*:*:*:node.js:*:* *cpe:2.3:a:vercel:next.js:15.6.0:canary48:*:*:*:node.js:*:* *cpe:2.3:a:vercel:next.js:15.6.0:canary49:*:*:*:node.js:*:* *cpe:2.3:a:vercel:next.js:15.6.0:canary5:*:*:*:node.js:*:* *cpe:2.3:a:vercel:next.js:15.6.0:canary50:*:*:*:node.js:*:* *cpe:2.3:a:vercel:next.js:15.6.0:canary51:*:*:*:node.js:*:* *cpe:2.3:a:vercel:next.js:15.6.0:canary52:*:*:*:node.js:*:* *cpe:2.3:a:vercel:next.js:15.6.0:canary53:*:*:*:node.js:*:* *cpe:2.3:a:vercel:next.js:15.6.0:canary54:*:*:*:node.js:*:* *cpe:2.3:a:vercel:next.js:15.6.0:canary55:*:*:*:node.js:*:* *cpe:2.3:a:vercel:next.js:15.6.0:canary56:*:*:*:node.js:*:* *cpe:2.3:a:vercel:next.js:15.6.0:canary57:*:*:*:node.js:*:* *cpe:2.3:a:vercel:next.js:15.6.0:canary6:*:*:*:node.js:*:* *cpe:2.3:a:vercel:next.js:15.6.0:canary7:*:*:*:node.js:*:* *cpe:2.3:a:vercel:next.js:15.6.0:canary8:*:*:*:node.js:*:* *cpe:2.3:a:vercel:next.js:15.6.0:canary9:*:*:*:node.js:*:* *cpe:2.3:a:vercel:next.js:*:*:*:*:*:node.js:*:* versions from (including) 13.3.0 up to (excluding) 14.2.35 *cpe:2.3:a:vercel:next.js:*:*:*:*:*:node.js:*:* versions from (including) 15.0.0 up to (excluding) 15.0.7 *cpe:2.3:a:vercel:next.js:*:*:*:*:*:node.js:*:* versions from (including) 15.1.0 up to (excluding) 15.1.11 *cpe:2.3:a:vercel:next.js:*:*:*:*:*:node.js:*:* versions from (including) 15.2.0 up to (excluding) 15.2.8 *cpe:2.3:a:vercel:next.js:*:*:*:*:*:node.js:*:* versions from (including) 15.3.0 up to (excluding) 15.3.8 *cpe:2.3:a:vercel:next.js:*:*:*:*:*:node.js:*:* versions from (including) 15.4.0 up to (excluding) 15.4.10 *cpe:2.3:a:vercel:next.js:*:*:*:*:*:node.js:*:* versions from (including) 15.5.0 up to (excluding) 15.5.9 *cpe:2.3:a:vercel:next.js:*:*:*:*:*:node.js:*:* versions from (including) 16.0.0 up to (excluding) 16.0.10 *cpe:2.3:a:vercel:next.js:15.6.0:canary58:*:*:*:node.js:*:* *cpe:2.3:a:vercel:next.js:15.6.0:canary59:*:*:*:node.js:*:* *cpe:2.3:a:vercel:next.js:16.1.0:-:*:*:*:node.js:*:* *cpe:2.3:a:vercel:next.js:16.1.0:canary0:*:*:*:node.js:*:* *cpe:2.3:a:vercel:next.js:16.1.0:canary1:*:*:*:node.js:*:* *cpe:2.3:a:vercel:next.js:16.1.0:canary10:*:*:*:node.js:*:* *cpe:2.3:a:vercel:next.js:16.1.0:canary11:*:*:*:node.js:*:* *cpe:2.3:a:vercel:next.js:16.1.0:canary12:*:*:*:node.js:*:* *cpe:2.3:a:vercel:next.js:16.1.0:canary13:*:*:*:node.js:*:* *cpe:2.3:a:vercel:next.js:16.1.0:canary14:*:*:*:node.js:*:* *cpe:2.3:a:vercel:next.js:16.1.0:canary15:*:*:*:node.js:*:* *cpe:2.3:a:vercel:next.js:16.1.0:canary16:*:*:*:node.js:*:* *cpe:2.3:a:vercel:next.js:16.1.0:canary17:*:*:*:node.js:*:* *cpe:2.3:a:vercel:next.js:16.1.0:canary18:*:*:*:node.js:*:* *cpe:2.3:a:vercel:next.js:16.1.0:canary2:*:*:*:node.js:*:* *cpe:2.3:a:vercel:next.js:16.1.0:canary3:*:*:*:node.js:*:* *cpe:2.3:a:vercel:next.js:16.1.0:canary4:*:*:*:node.js:*:* *cpe:2.3:a:vercel:next.js:16.1.0:canary5:*:*:*:node.js:*:* *cpe:2.3:a:vercel:next.js:16.1.0:canary6:*:*:*:node.js:*:* *cpe:2.3:a:vercel:next.js:16.1.0:canary7:*:*:*:node.js:*:* *cpe:2.3:a:vercel:next.js:16.1.0:canary8:*:*:*:node.js:*:* *cpe:2.3:a:vercel:next.js:16.1.0:canary9:*:*:*:node.js:*:*
    Added Reference Type Facebook, Inc.: https://react.dev/blog/2025/12/11/denial-of-service-and-source-code-exposure-in-react-server-components Types: Vendor Advisory
    Added Reference Type Facebook, Inc.: https://www.facebook.com/security/advisories/cve-2025-67779 Types: Vendor Advisory
  • New CVE Received by [email protected]

    Dec. 12, 2025

    Action Type Old Value New Value
    Added 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.
    Added CVSS V3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
    Added Reference https://react.dev/blog/2025/12/11/denial-of-service-and-source-code-exposure-in-react-server-components
    Added Reference https://www.facebook.com/security/advisories/cve-2025-67779
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days. Following chart shows the EPSS score history of the vulnerability.
Vulnerability Scoring Details
Base CVSS Score: 7.5
Attack Vector
Attack Complexity
Privileges Required
User Interaction
Scope
Confidentiality Impact
Integrity Impact
Availability Impact