Meta
react-server-dom-webpack
Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.
Official registry publication history is available at react-server-dom-webpack, but registry activity is not a publisher support boundary.
A missing support date does not mean the product is supported. CVE publication dates and affected-version ranges must not be interpreted as EOL dates.
CVE-observed version history
| CVE | Published | Affected versions | Fixed version information | Publisher evidence |
|---|---|---|---|---|
| CVE-2026-23864 | 26 Jan 2026 | 19.0.0 < 19.0.4; 19.1.0 < 19.1.5; 19.2.0 < 19.2.4 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-55184 | 11 Dec 2025 | 19.0.0 ≤ 19.0.1; 19.1.0 ≤ 19.1.2; 19.2.0 ≤ 19.2.1 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2025-55183 | 11 Dec 2025 | 19.0.0 ≤ 19.0.1; 19.1.0 ≤ 19.1.2; 19.2.0 ≤ 19.2.1 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
How this record is maintained
The CVE inventory is reconciled automatically from cve.blacktree.nl. Exact identity matches link to existing Lifecycle product or package histories. Unmatched products stay in a prioritised publisher-source research queue, and Lifecycle marks the date gap instead of inferring a support boundary from vulnerability data.