Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦 npm

CVE-2025-55184

HIGH

Denial of Service Vulnerability in React Server Components

Also known asGHSA-2m3v-v2m8-q956
Published
Dec 11, 2025
Updated
Apr 10, 2026
Affected
9 pkgs
Patched
9 / 9
Exploits
3 known

EPSS Exploitation Probability

via FIRST.org ↗
65.6%probability of exploitation in next 30 days
High Risk99th percentile+24.35%
3.76%29.1%54.5%79.9%18.0%65.6%Jan 26Apr 26Jun 26

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

9 pkgs affected
📦react-server-dom-parcel📦react-server-dom-turbopack📦react-server-dom-webpack📦react-server-dom-parcel📦react-server-dom-parcel📦react-server-dom-turbopack📦react-server-dom-turbopack📦react-server-dom-webpack+1 more

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.

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.

Affected Packages

9 total 9 fixed
EcosystemPackageVulnerable rangeFix
📦npmreact-server-dom-parcel19.0.0&&< 19.0.219.0.2
📦npmreact-server-dom-turbopack19.0.0&&< 19.0.219.0.2
📦npmreact-server-dom-webpack19.0.0&&< 19.0.219.0.2
📦npmreact-server-dom-parcel19.1.0&&< 19.1.319.1.3
📦npmreact-server-dom-parcel19.2.0&&< 19.2.219.2.2
📦npmreact-server-dom-turbopack19.1.0&&< 19.1.319.1.3
Exploits & PoCs
3

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for react-server-dom-parcel. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update react-server-dom-parcel to 19.0.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-55184 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether CVE-2025-55184 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2025-55184. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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.
O3 Security · Impact-Aware SCA

Is CVE-2025-55184 in your dependencies?

O3 detects CVE-2025-55184 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.