Skip to content
Noroxi
OSV ecosystem advisory

GHSA-mwv6-3258-q52c: Next Vulnerable to Denial of Service with Server Components

HighCVSS 7.5 · v3.1—No exploit Fix available

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.34, 15.0.6, 15.1.10.

Low priority for now. Upgrade to next (npm) 14.2.34, 15.0.6, 15.1.10 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

A vulnerability affects certain React packages for versions 19.0.0, 19.0.1, 19.1.0, 19.1.1, 19.1.2, 19.2.0, and 19.2.1 and frameworks that use the affected packages, including Next.js 15.x and 16.x using the App Router. The issue is tracked upstream as [CVE-2025-55184](https://www.cve.org/CVERecord?id=CVE-2025-55184). A malicious HTTP request can be crafted and sent to any App Router endpoint that, when deserialized, can cause the server process to hang and consume CPU. This can result in denial of service in unpatched environments.

Published
Dec 11, 2025
Updated
Sep 10, 2026
EPSS
—

Report tools

JSON

Action score

30

Monitor

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.

Follow GHSA-mwv6-3258-q52c

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Is the Next.js on your site affected?Scan JavaScript libraries

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Is the Next.js on your site affected?Scan JavaScript libraries

Is your version affected? Check it

Noroxi 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 help

Affected 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.

VendorProduct
npmnext

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 libraries

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
npmnextfrom 13.3.0 · before 14.2.3414.2.34
npmnextfrom 15.0.0-canary.0 · before 15.0.615.0.6
npmnextfrom 15.1.1-canary.0 · before 15.1.1015.1.10
npmnextfrom 15.2.0-canary.0 · before 15.2.715.2.7
npmnextfrom 15.3.0-canary.0 · before 15.3.715.3.7
npmnextfrom 15.4.0-canary.0 · before 15.4.915.4.9
npmnextfrom 15.5.1-canary.0 · before 15.5.815.5.8
npmnextfrom 15.6.0-canary.0 · before 15.6.0-canary.5915.6.0-canary.59
npmnextfrom 16.0.0-beta.0 · before 16.0.916.0.9
npmnextfrom 16.1.0-canary.0 · before 16.1.0-canary.1716.1.0-canary.17

Same product

npm: all records

Other highest-scoring records for the same primary product.

  • GHSA-8h8q-6873-q5fjNext.js Vulnerable to Denial of Service with Server Components
    30Monitor
  • GHSA-q4gf-8mx6-v5v3Next.js has a Denial of Service with Server Components
    30Monitor
  • GHSA-h25m-26qc-wcjfNext.js HTTP request deserialization can lead to DoS when using insecure React Server Components
    30Monitor

Published before and after this one in the same product

  • ← EarlierGHSA-5vj8-3v2h-h38vSep 4, 2020 · Remote Code Execution in next
    0Monitor
  • Later →GHSA-w37m-7fhw-fmv9Dec 11, 2025 · Next Server Actions Source Code Exposure
    21Monitor
  • Later →GHSA-5j59-xgg2-r9c4Dec 12, 2025 · Next has a Denial of Service with Server Components - Incomplete Fix Follow-Up
    30Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
npm:next14.2.34Package registry (OSV)
npm:next15.0.6Package registry (OSV)
npm:next15.1.10Package registry (OSV)
npm:next15.2.7Package registry (OSV)
npm:next15.3.7Package registry (OSV)
npm:next15.4.9Package registry (OSV)
npm:next15.5.8Package registry (OSV)
npm:next15.6.0-canary.59Package registry (OSV)
npm:next16.0.9Package registry (OSV)
npm:next16.1.0-canary.17Package 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-5j59-xgg2-r9c41 days apartNext has a Denial of Service with Server Components - Incomplete Fix Follow-Up
    30Monitor
  • GHSA-w37m-7fhw-fmv90 days apartNext Server Actions Source Code Exposure
    21Monitor
  • GHSA-2xp9-vwfh-vxw4271 days apartNext.js: Unauthenticated Remote Code Execution in Image Optimization API when AVIF files are used
    0Monitor

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

CVSS 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.

References

Show all references (3 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records