dbcve.org
ReactFramework / library · Facebook

CVE-2025-67779

HIGH · 7.5 CVSS v3.1 Published 2025-12-12
Fix available
A fix is available. Upgrade to 14.2.35 / 15.0.7 or later.
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
It was found that the fix addressing CVE-2025-55184 in React Server Components was incomplete and does not prevent a denial of service attack in a specific case. React Server Components versions 19.0.2, 19.1.3 and 19.2.2 are affected, allowing unsafe deserialization of payloads from HTTP requests to Server Function endpoints. This can cause an infinite loop that hangs the server process and may prevent future HTTP requests from being served.

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 · moderate confidence

React Server Components versions 19.0.2, 19.1.3, and 19.2.2 have an incomplete fix from CVE-2025-55184 that allows unsafe deserialization of payloads from HTTP requests to Server Function endpoints, triggering an infinite loop that hangs the server and prevents future requests.

MitigationUpgrade React Server Components to a version beyond 19.2.2 once the patched release is available, and implement request timeout limits on Server Function endpoints as a defensive measure.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ReactFramework / library
Affected:= 19.0.2= 19.1.3= 19.2.2
Next.jsApplication
Affected:>= 13.3.0, < 14.2.35>= 15.0.0, < 15.0.7>= 15.1.0, < 15.1.11>= 15.2.0, < 15.2.8>= 15.3.0, < 15.3.8>= 15.4.0, < 15.4.10>= 15.5.0, < 15.5.9>= 16.0.0, < 16.0.10= 15.6.0= 16.1.0

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 version
    Check package.json or run 'npm list react' (or pnpm/yarn equivalent) to see the installed react package version
    Affected if Installed version is exactly 19.0.2, 19.1.3, or 19.2.2
  2. Identify installed Next.js version
    Check package.json or run 'npm list next' to see the installed next package version
    Affected if Installed version matches any of the vulnerable ranges: >= 13.3.0 and < 14.2.35; >= 15.0.0 and < 15.0.7; >= 15.1.0 and < 15.1.11; >= 15.2.0 and < 15.2.8; >= 15.3.0 and < 15.3.8; >= 15.4.0 and < 15.4.10; >= 15.5.0 and < 15.5.9; >= 16.0.0 and < 16.0.10; equals 15.6.0; or equals 16.1.0
  3. Determine if Server Functions are in use
    Search codebase for 'use server' directives in .js/.ts/.jsx/.tsx files, or check for Server Action definitions in Next.js applications
    Affected if Server Functions or Server Actions are implemented and exposed via HTTP endpoints

You are affected if you have a vulnerable React or Next.js version installed AND you use Server Function endpoints accessible via HTTP requests.

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
Upgrade available Upgrade to 14.2.35 / 15.0.7 / 15.1.11 or later
Fixed in 14.2.3515.0.715.1.11
Interim mitigation

Upgrade React Server Components to a version beyond 19.2.2 once the patched release is available, and implement request timeout limits on Server Function endpoints as a defensive measure.

Recommended fix High confidence

Next.js: 14.2.35+ or 15.2.8+ (latest 15.x recommended); React: 19.2.3+

  1. 1. For Next.js applications: Run 'npm list next' to confirm current version
  2. 2. If using Next.js 14.x (14.3.x or 14.2.x): Upgrade to version 14.2.35 or later
  3. 3. If using Next.js 15.x: Upgrade to version 15.2.8 or later (recommended: 15.2.9 or latest 15.x stable)
  4. 4. Run 'npm install next@latest' or 'npm install [email protected]' to apply the fix
  5. 5. If using standalone React Server Components without Next.js: Upgrade React to version 19.2.3 or later
  6. 6. Verify the upgrade by testing Server Function endpoints for proper behavior
Caveat Minor: This is a security patch with no expected breaking changes; ensure thorough testing of Server Function endpoints after upgrade

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

Fix this in React Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-67779 — 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-2025-67779 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