react-server-dom-webpack
npm package
Overview
Package versions
| Versions | Range | Direct vulnerabilities |
|---|---|---|
| 19.3.1 | and later versions | 0C0H0M0L |
| 19.3.0 | up to 19.3.1 | 1C0H0M0L |
| 19.2.9 | up to 19.3.0 | 0C0H0M0L |
| 19.2.8 | up to 19.2.9 | 1C0H0M0L |
| 19.2.6 | up to 19.2.8 | 1C1H0M0L |
| 19.2.5 | up to 19.2.6 | 1C2H0M0L |
| 19.2.4 | up to 19.2.5 | 1C3H0M0L |
| 19.2.3 | up to 19.2.4 | 1C4H0M0L |
| 19.2.2 | up to 19.2.3 | 1C5H0M0L |
| 19.2.1 | up to 19.2.2 | 1C5H1M0L |
| 19.2.0 | up to 19.2.1 | 2C5H1M0L |
| 19.2.0-canary-63779030-20250328 | up to 19.2.0 | 0C1H0M0L |
| 19.1.10 | up to 19.2.0-canary-63779030-20250328 | 0C0H0M0L |
| 19.1.9 | up to 19.1.10 | 1C0H0M0L |
| 19.1.7 | up to 19.1.9 | 1C1H0M0L |
| 19.1.6 | up to 19.1.7 | 1C2H0M0L |
| 19.1.5 | up to 19.1.6 | 1C3H0M0L |
| 19.1.4 | up to 19.1.5 | 1C4H0M0L |
| 19.1.3 | up to 19.1.4 | 1C5H0M0L |
| 19.1.2 | up to 19.1.3 | 1C5H1M0L |
| 19.1.0 | up to 19.1.2 | 2C5H1M0L |
| 19.1.0-canary-7130d0c6-20241212 | up to 19.1.0 | 0C1H0M0L |
| 19.0.9 | up to 19.1.0-canary-7130d0c6-20241212 | 0C0H0M0L |
| 19.0.8 | up to 19.0.9 | 1C0H0M0L |
| 19.0.6 | up to 19.0.8 | 1C1H0M0L |
| 19.0.5 | up to 19.0.6 | 1C2H0M0L |
| 19.0.4 | up to 19.0.5 | 1C3H0M0L |
| 19.0.3 | up to 19.0.4 | 1C4H0M0L |
| 19.0.2 | up to 19.0.3 | 1C5H0M0L |
| 19.0.1 | up to 19.0.2 | 1C5H1M0L |
| 19.0.0 | up to 19.0.1 | 2C5H1M0L |
| before 19.0.0 | all earlier versions | 0C0H0M0L |
No known vulnerabilities in 19.3.1 and later versions
Nothing in our data affects this version.
32 ranges in total. Each row is a range of versions with the same vulnerabilities, newest first. The data names only the versions where something changes (first affected, fixed), so the versions in between are a range.
Vulnerabilities · 9
| CVE | Severity | Published | Vulnerable | Fixed in |
|---|---|---|---|---|
| CVE-2026-126187React: Unauthenticated Remote Code Execution in React Server Components | CRITICAL | 10 Nov 2026 | >=19.0.0, <19.0.9>=19.1.0, <19.1.10>=19.2.0, <19.2.9>=19.3.0, <19.3.1 | 19.0.919.1.1019.2.919.3.1 |
| CVE-2026-44907react-server-dom: Denial of Service in Server Functions | HIGH | 21 Jul 2026 | >=19.0.0, <19.0.8>=19.1.0, <19.1.9>=19.2.0, <19.2.8 | 19.0.819.1.919.2.8 |
| CVE-2026-23870react-server-dom-webpack: react-server-dom-parcel: react-server-dom-turbopack: React Server DOM: Denial of Service via specially crafted HTTP requests | HIGH | 6 May 2026 | >=19.0.0, <19.0.6>=19.1.0, <19.1.7>=19.2.0, <19.2.6 | 19.0.619.1.719.2.6 |
| CVE-2026-23869react-server-dom-parcel: react-server-dom-turbopack: react-server-dom-webpack: denial of service via specially crafted HTTP requests to Server Function endpoints | HIGH | 8 Apr 2026 | >=19.0.0, <19.0.5>=19.1.0, <19.1.6>=19.2.0, <19.2.5 | 19.0.519.1.619.2.5 |
| CVE-2026-23864react-server-dom-webpack: react-server-dom-parcel: reactreact-server-dom-turbopack: React Server Components: Denial of Service via specially crafted HTTP requests | HIGH | 26 Jan 2026 | >=19.2.0-canary-63779030-20250328, <19.2.4>=19.1.0-canary-7130d0c6-20241212, <19.1.5>=19.0.0, <19.0.4 | 19.2.419.1.519.0.4 |
| CVE-2025-67779next: React Server Components: Denial of Service via Unsafe Deserialization | HIGH | 12 Dec 2025 | >=19.0.2, <19.0.3>=19.1.3, <19.1.4>=19.2.2, <19.2.3 | 19.0.319.1.419.2.3 |
| CVE-2025-55184next: React Server Components: Denial of Service via unsafe HTTP deserialization | HIGH | 11 Dec 2025 | >=19.0.0, <19.0.2>=19.1.0, <19.1.3>=19.2.0, <19.2.2 | 19.0.219.1.319.2.2 |
| CVE-2025-55183next: React Server Components: Source code exposure through crafted HTTP request | MEDIUM | 11 Dec 2025 | >=19.0.0, <19.0.2>=19.1.0, <19.1.3>=19.2.0, <19.2.2 | 19.0.219.1.319.2.2 |
| CVE-2025-55182next: React Server Components: Pre-authentication remote code execution via unsafe deserialization | CRITICAL | 3 Dec 2025 | >=19.0.0, <19.0.1>=19.1.0, <19.1.2>=19.2.0, <19.2.1 | 19.0.119.1.219.2.1 |
OX Radar and Response Center
Find threats in your stack.
OX Radar can check high-priority threats, like critical package CVEs, against your context.
Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.