Categories
CVE-2026-23870 high CVSS 7.5

Vulnerability in react-server-dom-parcel (CVE-2026-23870)

Summary

Vulnerability in react-server-dom-parcel (CVE-2026-23870). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 19.2.6 or later.

Original description

The description as published by the source.

A denial of service vulnerability could be triggered by sending specially crafted HTTP requests to server function endpoints, this could lead to server crashes, out-of-memory exceptions or excessive CPU usage; affecting the following packages: react-server-dom-webpack, react-server-dom-parcel, react-server-dom-turbopack (versions 19.0.0 through 19.0.5, 19.1.0 through 19.1.6, and 19.2.0 through 19.2.5).

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-23870 has been found in react-server-dom-parcel.
Risk of unauthorized operations or information disclosure. CVSS score: 7.5/10.
What to do: upgrade react-server-dom-parcel to 19.2.6 or later.
If unsure, ask your IT team or search "react-server-dom-parcel CVE-2026-23870" on the vendor's site.

CVE-2026-23870 (react-server-dom-parcel) — CWE-400 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 19.2.6 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-400) exists in react-server-dom-parcel.

📍 Affected scope

Check the vendor advisory for the affected versions of react-server-dom-parcel.

🔥 Severity

Severity: High (CVSS 7.5/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 19.2.6.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'react-server-dom-parcel' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    grep -r 'react-server-dom-parcel' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で react-server-dom-parcel を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch
    Upgrade react-server-dom-parcel to 19.2.6

    ステージング環境で 19.2.6 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

npm react-server-dom-parcel
[{"type":"SEMVER","events":[{"introduced":"19.2.0"},{"fixed":"19.2.6"}]}]
npm react-server-dom-turbopack
[{"type":"SEMVER","events":[{"introduced":"19.2.0"},{"fixed":"19.2.6"}]}]
npm react-server-dom-webpack
[{"type":"SEMVER","events":[{"introduced":"19.2.0"},{"fixed":"19.2.6"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details