CVE-2025-55184VulnerabilityPublished 11 Dec 2025Updated 15 Dec 2025

CVE-2025-55184: Meta react-server-dom-webpack · Deserialization of Untrusted Data. Uncontrolled Resource Consumption

Affects Meta react-server-dom-webpackSource CVE Database V5

Not known to be exploited · public detection template (Nuclei) · 66% EPSS · CVSS 7.5 High.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 66.6% chance of exploitation in 30 days – higher than 99% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 11 Dec 2025
Detectable: evidence found.
nuclei template: React Server Components - Denial of Service
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
npmreact-server-dom-parcel`pkg:npm/react-server-dom-parcel`Other threats	Affected =19.0.0 =19.1.0 =19.2.0	Fixed in–
npmreact-server-dom-turbopack`pkg:npm/react-server-dom-turbopack`Other threats	Affected =19.0.0 =19.1.0 =19.2.0	Fixed in–
npmreact-server-dom-webpack`pkg:npm/react-server-dom-webpack`Other threats	Affected =19.0.0 =19.1.0 =19.2.0	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Monitor Meta’s official channels for patches addressing CVE-2025-55184 and apply them promptly once available. 2. Until patches are released, implement strict input validation and sanitization on all data received by Server Function endpoints to prevent malicious payloads from triggering unsafe deserialization. 3. Deploy Web Application Firewalls (WAFs) with custom rules to detect and block suspicious payloads targeting react-server-dom-webpack endpoints. 4. Implement rate limiting on HTTP requests to Server Function endpoints to reduce the risk of resource exhaustion from repeated malicious requests. 5. Consider isolating or sandboxing the server processes handling deserialization to limit the impact of potential infinite loops or hangs. 6. Conduct thorough code reviews and security testing focusing on deserialization logic in React Server Components. 7. Prepare incident response plans to quickly identify and mitigate denial of service attacks exploiting this vulnerability. 8. Educate development teams about the risks of unsafe deserialization and best practices for secure coding in React Server Components.

Description

A pre-authentication denial of service vulnerability exists in React Server Components versions 19.0.0, 19.0.1 19.1.0, 19.1.1, 19.1.2, 19.2.0 and 19.2.1, including the following packages: react-server-dom-parcel, react-server-dom-turbopack, and react-server-dom-webpack. The vulnerable code unsafely deserializes payloads from HTTP requests to Server Function endpoints, which can cause an infinite loop that hangs the server process and may prevent future HTTP requests from being served.

Impact

For European organizations, the primary impact of CVE-2025-55184 is denial of service, which can disrupt web services and applications built using affected React Server Components. This can lead to downtime, loss of customer trust, and potential financial losses, especially for e-commerce, online services, and critical infrastructure relying on these technologies. The vulnerability’s pre-authentication nature means attackers can exploit it without credentials, increasing the risk of widespread attacks. Organizations with high traffic websites or those providing essential services may experience significant operational disruptions. Additionally, prolonged outages could affect compliance with European regulations such as GDPR if service availability commitments are not met. The impact is mostly on availability; confidentiality and integrity are not directly affected. The risk is heightened in countries with large digital economies and extensive use of React-based frameworks in web development, where attackers may target high-profile or critical service providers to maximize disruption.

CWE-502Deserialization of Untrusted Data (opens in a new tab)
Base weaknessLikelihood of exploit: MediumCWE Top 25 (2025): #15OWASP Top 10 A08:2025: Software or Data Integrity Failures (opens in a new tab)
The product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid.
Architecture and Design · Implementation
If available, use the signing/sealing features of the programming language to assure that deserialized data has not been tainted. For example, a hash-based message authentication code (HMAC) could be used to ensure that data has not been modified.
Implementation
When deserializing data, populate a new object rather than just deserializing. The result is that the data flows through safe input validation and that the functions are safe.
Implementation
Explicitly define a final object() to prevent deserialization.
OWASP Cheat Sheets
Abuse Case (opens in a new tab)
Deserialization (opens in a new tab)
XML Security (opens in a new tab)
XML External Entity Prevention (opens in a new tab)
Software Supply Chain Security (opens in a new tab)
OWASP ASVS 4.0.3
V1.5.2 (opens in a new tab)
V5.5.3 (opens in a new tab)
V5.5.1 (opens in a new tab)
Attack patterns
Object Injection (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 19 Dec 2025, 05:12 UTC

Public exploits and detectiona Nuclei detection template

WeaknessesCWE-502

Technical details

References

Community reviews

Related threats