Skip to content
Noroxi
CVE-2025-55184· NVD / CVE Program· CNA Meta

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.

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.

HighCVSS 7.5 · v3.1—Proof of concept Fix available
Published
Dec 11, 2025
Updated
Jun 17, 2026
EPSS
66.9% · 99th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

50

Plan

Add it to your regular patch cycle.

CVSS
30 / 40 · 7.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
20 / 30 · 66.9%

CISA SSVC decision

Exploitation
proof of concept
Automatable
yes
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · Meta
7.5
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Affected systems

VendorProduct
facebookreact
vercelnext.js

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • facebook react19.0.0 and later · before 19.0.2
  • facebook react19.1.0 and later · before 19.1.3
  • facebook react19.2.0 and later · before 19.2.2
  • vercel next.js13.3.0 and later · before 14.2.35
  • vercel next.js15.0.0 and later · before 15.0.7
  • vercel next.js15.1.0 and later · before 15.1.11
  • vercel next.js15.2.0 and later · before 15.2.8
  • vercel next.js15.3.0 and later · before 15.3.8
  • vercel next.js15.4.0 and later · before 15.4.10
  • vercel next.js15.5.0 and later · before 15.5.9
  • vercel next.js16.0.0 and later · before 16.0.10
  • vercel next.js15.6.0
  • vercel next.js16.1.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Meta). Independent of NVD's CPE analysis and usually ahead of it.

  • Meta react-server-dom-parcel

    • 19.0.0 and later · up to and including 19.0.1affected · semver
    • 19.1.0 and later · up to and including 19.1.2affected · semver
    • 19.2.0 and later · up to and including 19.2.1affected · semver
  • Meta react-server-dom-turbopack

    • 19.0.0 and later · up to and including 19.0.1affected · semver
    • 19.1.0 and later · up to and including 19.1.2affected · semver
    • 19.2.0 and later · up to and including 19.2.1affected · semver
  • Meta react-server-dom-webpack

    • 19.0.0 and later · up to and including 19.0.1affected · semver
    • 19.1.0 and later · up to and including 19.1.2affected · semver
    • 19.2.0 and later · up to and including 19.2.1affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
npmreact-server-dom-parcelfrom 19.0.0 · before 19.0.219.0.2
npmreact-server-dom-parcelfrom 19.1.0 · before 19.1.319.1.3
npmreact-server-dom-parcelfrom 19.2.0 · before 19.2.219.2.2
npmreact-server-dom-turbopackfrom 19.0.0 · before 19.0.219.0.2
npmreact-server-dom-turbopackfrom 19.1.0 · before 19.1.319.1.3
npmreact-server-dom-turbopackfrom 19.2.0 · before 19.2.219.2.2
npmreact-server-dom-webpackfrom 19.0.0 · before 19.0.219.0.2
npmreact-server-dom-webpackfrom 19.1.0 · before 19.1.319.1.3
npmreact-server-dom-webpackfrom 19.2.0 · before 19.2.219.2.2

Other highest-scoring records for the same primary product.

  • CVE-2025-55182A pre-authentication remote code execution vulnerability exists in React Server Components versions 19.0.0, 19.1.0, 19.1.1, and 19.2.0 incluKEV
    100Now
  • CVE-2025-67779It was found that the fix addressing CVE-2025-55184 in React Server Components was incomplete and does not prevent a denial of service attac
    36Monitor
  • CVE-2026-23864Multiple denial of service vulnerabilities exist in React Server Components, affecting the following packages: react-server-dom-parcel, reac
    31Monitor
  • CVE-2018-6341React applications which rendered to HTML using the ReactDOMServer API were not escaping user-supplied attribute names at render-time.
    25Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
npm:react-server-dom-parcel19.0.2Package registry (OSV)
npm:react-server-dom-parcel19.1.3Package registry (OSV)
npm:react-server-dom-parcel19.2.2Package registry (OSV)
npm:react-server-dom-turbopack19.0.2Package registry (OSV)
npm:react-server-dom-turbopack19.1.3Package registry (OSV)
npm:react-server-dom-turbopack19.2.2Package registry (OSV)
npm:react-server-dom-webpack19.0.2Package registry (OSV)
npm:react-server-dom-webpack19.1.3Package registry (OSV)
npm:react-server-dom-webpack19.2.2Package registry (OSV)

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

  • Nuclei detection template ×1
  • Proof-of-concept repository on GitHub ×9

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
SourceKindDate
Nuclei detection templateNuclei template CVE-2025-55184 —
Proof-of-concept repository on GitHubstars:32025-12-12
Proof-of-concept repository on GitHubstars:72025-12-12
Proof-of-concept repository on GitHubstars:02025-12-12
Proof-of-concept repository on GitHubstars:222025-12-13
Proof-of-concept repository on GitHubstars:22025-12-13
Proof-of-concept repository on GitHubstars:12025-12-14
Proof-of-concept repository on GitHubstars:02025-12-17
Proof-of-concept repository on GitHubstars:12025-12-19
Proof-of-concept repository on GitHubstars:02026-01-14

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. Published
  2. First PoCsame day
  3. TodaySep 29, 2026+292 d
EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2025-551828 days apartA pre-authentication remote code execution vulnerability exists in React Server Components versions 19.0.0, 19.1.0, 19.1.1, and 19.2.0 incluKEV
    100Now
  • CVE-2025-677790 days apartIt was found that the fix addressing CVE-2025-55184 in React Server Components was incomplete and does not prevent a denial of service attac
    36Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

CVSS vector

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

nvd-secondary

Root cause

Data received over the network is deserialized into the language’s native object format without verifying its source. Code paths inside the object can be triggered during deserialization.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

python
payload = sock.recv(65536)job = pickle.loads(payload)

Fixed

python
payload = sock.recv(65536)if not hmac.compare_digest(sign(payload), header_sig):    raise PermissionError("invalid signature")job = JobSchema.validate(json.loads(payload))

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records