GHSA-5j59-xgg2-r9c4: Next has a Denial of Service with Server Components - Incomplete Fix Follow-Up
Noroxi assessment
Priority: Monitor (action score 30/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: next (npm) 14.2.35, 15.0.7, 15.1.11.
Low priority for now. Upgrade to next (npm) 14.2.35, 15.0.7, 15.1.11 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: OSV
It was discovered that the fix for [CVE-2025-55184](https://github.com/advisories/GHSA-2m3v-v2m8-q956) in React Server Components was incomplete and did not fully mitigate denial-of-service conditions across all payload types. As a result, certain crafted inputs could still trigger excessive resource consumption. This vulnerability affects React versions 19.0.2, 19.1.3, and 19.2.2, as well as frameworks that bundle or depend on these versions, including Next.js 13.x, 14.x, 15.x, and 16.x when using the App Router. The issue is tracked upstream as [CVE-2025-67779](https://www.cve.org/CVERecord?id=CVE-2025-67779). A malicious actor can send a specially crafted HTTP request to a Server Function endpoint that, when deserialized, causes the React Server Components runtime to enter an infinite loop. This can lead to sustained CPU consumption and cause the affected server process to become unresponsive, resulting in a denial-of-service condition in unpatched environments.
- Published
- Dec 12, 2025
- Updated
- Sep 10, 2026
- EPSS
- —
- CWE
- CWE-1395
Report tools
Action score
30
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · —
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is the Next.js on your site affected?Scan JavaScript libraries
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| npm | next | pkg:npm/next |
Is the Next.js on your site affected?
The free JavaScript library scanner reads the Next.js version from the files your site loads, matches this record and other known vulnerabilities, and gives the safe version on the same branch. If the version can't be read, it says so. No account needed.
Scan JavaScript librariesPackage-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| npm | next | from 13.3.1-canary.0 · before 14.2.35 | 14.2.35 |
| npm | next | from 15.0.6 · before 15.0.7 | 15.0.7 |
| npm | next | from 15.1.10 · before 15.1.11 | 15.1.11 |
| npm | next | from 15.2.7 · before 15.2.8 | 15.2.8 |
| npm | next | from 15.3.7 · before 15.3.8 | 15.3.8 |
| npm | next | from 15.4.9 · before 15.4.10 | 15.4.10 |
| npm | next | from 15.5.8 · before 15.5.9 | 15.5.9 |
| npm | next | from 15.6.0-canary.59 · before 15.6.0-canary.60 | 15.6.0-canary.60 |
| npm | next | from 16.0.9 · before 16.0.10 | 16.0.10 |
| npm | next | from 16.1.0-canary.17 · before 16.1.0-canary.19 | 16.1.0-canary.19 |
Same product
npm: all recordsOther highest-scoring records for the same primary product.
- GHSA-8h8q-6873-q5fjNext.js Vulnerable to Denial of Service with Server Components30Monitor
- GHSA-q4gf-8mx6-v5v3Next.js has a Denial of Service with Server Components30Monitor
- GHSA-h25m-26qc-wcjfNext.js HTTP request deserialization can lead to DoS when using insecure React Server Components30Monitor
Published before and after this one in the same product
- ← EarlierGHSA-mwv6-3258-q52cDec 11, 2025 · Next Vulnerable to Denial of Service with Server Components30Monitor
- ← EarlierGHSA-w37m-7fhw-fmv9Dec 11, 2025 · Next Server Actions Source Code Exposure21Monitor
- Later →GHSA-2xp9-vwfh-vxw4Sep 8, 2026 · Next.js: Unauthenticated Remote Code Execution in Image Optimization API when AVIF files are used0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| npm:next | 14.2.35 | Package registry (OSV) |
| npm:next | 15.0.7 | Package registry (OSV) |
| npm:next | 15.1.11 | Package registry (OSV) |
| npm:next | 15.2.8 | Package registry (OSV) |
| npm:next | 15.3.8 | Package registry (OSV) |
| npm:next | 15.4.10 | Package registry (OSV) |
| npm:next | 15.5.9 | Package registry (OSV) |
| npm:next | 15.6.0-canary.60 | Package registry (OSV) |
| npm:next | 16.0.10 | Package registry (OSV) |
| npm:next | 16.1.0-canary.19 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- GHSA-mwv6-3258-q52c1 days apartNext Vulnerable to Denial of Service with Server Components30Monitor
- GHSA-w37m-7fhw-fmv91 days apartNext Server Actions Source Code Exposure21Monitor
- GHSA-2xp9-vwfh-vxw4270 days apartNext.js: Unauthenticated Remote Code Execution in Image Optimization API when AVIF files are used0Monitor
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-1395 · Dependency on Vulnerable Third-Party ComponentCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
osv
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.