Skip to content
Fencer Intel
high 7.5

CVE-2025-67779 in the critical feed json

Next has a Denial of Service with Server Components - Incomplete Fix Follow-Up

published 10mo ago modified last mo. also EUVD-2025-202926 , GHSA-5j59-xgg2-r9c4 , GHSA-7gmr-mq3h-m5h9

cvss
7.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
20.0%
EPSS 20.0% chance of exploitation in 30 days, percentile 97%
public exploits
0
none known

Summary

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.

Patch / fix

  • npm next 14.2.35, 15.0.7, 15.1.11, 15.2.8, 15.3.8, 15.4.10, 15.5.9, 15.6.0-canary.60, 16.0.10, 16.1.0-canary.19
  • npm react-server-dom-parcel 19.0.3, 19.1.4, 19.2.3
  • npm react-server-dom-turbopack 19.0.3, 19.1.4, 19.2.3
  • npm react-server-dom-webpack 19.0.3, 19.1.4, 19.2.3
  • vercel next.js 14.2.35, 15.0.7, 15.1.11, 15.2.8, 15.3.8, 15.4.10, 15.5.9, 16.0.10

Is CVE-2025-67779 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2025-67779 updated cvss 7.5

next: React Server Components: Denial of Service via Unsafe Deserialization

  • Red Hat Enterprise Linux 7 firefox Red Hat Enterprise Linux 8 firefox, thunderbird Red Hat Enterprise Linux 9 firefox, dotnet7.0, dotnet-host, firefox-x11, thunderbird, dotnet-sdk-7.0, +9 more Red Hat Enterprise Linux 10 firefox, thunderbird Red Hat Enterprise Linux AI (RHEL AI) 3 rhelai3/bootc-cuda-rhel9, rhelai3/disk-image-cuda-rhel9 Red Hat Trusted Artifact Signer rhtas/rekor-search-ui-rhel9
    +2 more products
    Red Hat streams for Apache Kafka 2 com.github.streamshub-console Red Hat streams for Apache Kafka 3 com.github.streamshub-console
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
10mo ago

Exploit prediction

19.99% chance of exploitation in the next 30 days, higher than 97% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
GitHub 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected packages

ecosystem package affected fixed in
npm next
>=13.3.1-canary.0, <14.2.35
>=15.0.6, <15.0.7
>=15.1.10, <15.1.11
>=15.2.7, <15.2.8
>=15.3.7, <15.3.8
>=15.4.9, <15.4.10
>=15.5.8, <15.5.9
>=15.6.0-canary.59, <15.6.0-canary.60
>=16.0.9, <16.0.10
>=16.1.0-canary.17, <16.1.0-canary.19
14.2.35
15.0.7
15.1.11
15.2.8
15.3.8
15.4.10
15.5.9
15.6.0-canary.60
16.0.10
16.1.0-canary.19
npm react-server-dom-parcel
>=19.0.2, <19.0.3
>=19.1.3, <19.1.4
>=19.2.2, <19.2.3
19.0.3
19.1.4
19.2.3
npm react-server-dom-turbopack
>=19.0.2, <19.0.3
>=19.1.3, <19.1.4
>=19.2.2, <19.2.3
19.0.3
19.1.4
19.2.3
npm react-server-dom-webpack
>=19.0.2, <19.0.3
>=19.1.3, <19.1.4
>=19.2.2, <19.2.3
19.0.3
19.1.4
19.2.3

Affected products

  • Meta react-server-dom-parcel
  • Meta react-server-dom-turbopack
  • Meta react-server-dom-webpack

Classification

Weakness
  • CWE-502 Deserialization of Untrusted Data
  • CWE-400 Uncontrolled Resource Consumption
  • CWE-1395 Dependency on Vulnerable Third-Party Component
Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

The maintainers of vercel/next.js published their own advisory on GitHub. Reviewed sources take precedence over it.