dbcve.org
Uncontrolled Resource ConsumptionWeakness · CWE-400

CVE-2026-23869

HIGH · 7.5 CVSS v3.1 Published 2026-04-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A denial of service vulnerability exists in React Server Components, affecting the following packages: react-server-dom-parcel, react-server-dom-turbopack and react-server-dom-webpack (versions 19.0.0 through 19.0.4, 19.1.0 through 19.1.5, and 19.2.0 through 19.2.4). The vulnerability is triggered by sending specially crafted HTTP requests to Server Function endpoints.The payload of the HTTP request causes excessive CPU usage for up to a minute ending in a thrown error that is catchable.

In the news

Third-party coverage
Trending covered by 1 outlet this week · latest 4mo ago

Surfaced from public web coverage — external links open in a new tab.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A denial of service vulnerability in React Server Components (react-server-dom-parcel, react-server-dom-turbopack, react-server-dom-webpack versions 19.0.0-19.0.4, 19.1.0-19.1.5, and 19.2.0-19.2.4) allows attackers to trigger excessive CPU usage for up to a minute by sending specially crafted HTTP requests to Server Function endpoints, resulting in a catchable error and service disruption.

MitigationUpgrade react-server-dom packages to versions 19.0.5+, 19.1.6+, or 19.2.5+ (or latest stable). As a temporary measure, implement rate limiting and request validation on Server Function endpoints.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed react-server-dom-* package versions
    Run 'npm list react-server-dom-parcel react-server-dom-turbopack react-server-dom-webpack' or inspect your package-lock.json to find the exact versions installed
    Affected if The installed version falls within 19.0.0-19.0.4, 19.1.0-19.1.5, or 19.2.0-19.2.4 for any of these packages
  2. Confirm Server Function usage in your application
    Search your codebase for 'use server' directives or look for files importing from 'react-server-dom-*' packages that handle server function calls
    Affected if Your application uses React Server Components with Server Functions, which exposes the affected endpoints
  3. Check for exposed Server Function HTTP endpoints
    Review your server configuration files (such as webpack config, turbopack config, or parcel config) and application entry points to identify where server function handlers are registered and exposed over HTTP
    Affected if Server Function handlers are exposed via HTTP (typical in server-side rendering setups)

You are affected if you have any react-server-dom-parcel, react-server-dom-turbopack, or react-server-dom-webpack packages installed within the affected version ranges AND your application exposes Server Function endpoints over HTTP.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade react-server-dom packages to versions 19.0.5+, 19.1.6+, or 19.2.5+ (or latest stable). As a temporary measure, implement rate limiting and request validation on Server Function endpoints.

Recommended fix Moderate confidence

React 19.2.5 or later (or latest 19.x stable release)

  1. Check your package.json for react and react-server-dom-* dependencies
  2. Run 'npm list react react-server-dom-parcel react-server-dom-turbopack react-server-dom-webpack' to verify currently installed versions
  3. If using React 19.x, upgrade to the latest 19.x release (19.2.5 or later) using: npm install react@latest react-dom@latest
  4. Alternatively, upgrade individual packages: npm install react-server-dom-parcel@latest react-server-dom-turbopack@latest react-server-dom-webpack@latest
  5. After upgrading, test Server Function endpoints to ensure normal operation
  6. Monitor for any breaking changes in React 19.x release notes if upgrading major versions
Caveat React 19.x may have breaking changes from earlier versions; review React 19 release notes before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-23869 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-23869 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data