What is GHSA-MWV6-3258-Q52C?

GHSA-MWV6-3258-Q52C is a high-severity uncontrolled resource consumption vulnerability in next (npm), affecting versions >= 13.3.0, < 14.2.34. It is fixed in 14.2.34, 15.0.6, 15.1.10, 15.2.7, 15.3.7, 15.4.9, 15.5.8, 15.6.0-canary.59, 16.0.9, 16.1.0-canary.17. Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service.

How severe is GHSA-MWV6-3258-Q52C?

GHSA-MWV6-3258-Q52C has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of next are affected by GHSA-MWV6-3258-Q52C?

next (npm) versions >= 13.3.0, < 14.2.34 is affected.

Is GHSA-MWV6-3258-Q52C exploitable, and should I be worried?

Whether GHSA-MWV6-3258-Q52C is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether GHSA-MWV6-3258-Q52C is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

GHSA-MWV6-3258-Q52C in next | Intelligent Application Security

Q: How severe is GHSA-MWV6-3258-Q52C?

GHSA-MWV6-3258-Q52C has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of next are affected by GHSA-MWV6-3258-Q52C?

next (npm) versions >= 13.3.0, < 14.2.34 is affected.

Q: Is there a fix for GHSA-MWV6-3258-Q52C?

Yes. GHSA-MWV6-3258-Q52C is fixed in 14.2.34, 15.0.6, 15.1.10, 15.2.7, 15.3.7, 15.4.9, 15.5.8, 15.6.0-canary.59, 16.0.9, 16.1.0-canary.17. Upgrade to this version or later.

Q: Is GHSA-MWV6-3258-Q52C exploitable, and should I be worried?

Whether GHSA-MWV6-3258-Q52C is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether GHSA-MWV6-3258-Q52C is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix GHSA-MWV6-3258-Q52C?

Upgrade: next to 14.2.34 or later, next to 15.0.6 or later, next to 15.1.10 or later, next to 15.2.7 or later, next to 15.3.7 or later, next to 15.4.9 or later, next to 15.5.8 or later, next to 15.6.0-canary.59 or later, next to 16.0.9 or later, next to 16.1.0-canary.17 or later.

Summary

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.

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.

Impact

Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service. Typical impact: denial of service.

GHSA-MWV6-3258-Q52C has a CVSS score of 7.5 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (14.2.34, 15.0.6, 15.1.10, 15.2.7, 15.3.7, 15.4.9, 15.5.8, 15.6.0-canary.59, 16.0.9, 16.1.0-canary.17); upgrading removes the vulnerable code path.

Affected versions

next (>= 13.3.0, < 14.2.34) next (>= 15.0.0-canary.0, < 15.0.6) next (>= 15.1.1-canary.0, < 15.1.10) next (>= 15.2.0-canary.0, < 15.2.7) next (>= 15.3.0-canary.0, < 15.3.7) next (>= 15.4.0-canary.0, < 15.4.9) next (>= 15.5.1-canary.0, < 15.5.8) next (>= 15.6.0-canary.0, < 15.6.0-canary.59) next (>= 16.0.0-beta.0, < 16.0.9) next (>= 16.1.0-canary.0, < 16.1.0-canary.17)

Security releases

next → 14.2.34 (npm) next → 15.0.6 (npm) next → 15.1.10 (npm) next → 15.2.7 (npm) next → 15.3.7 (npm) next → 15.4.9 (npm) next → 15.5.8 (npm) next → 15.6.0-canary.59 (npm) next → 16.0.9 (npm) next → 16.1.0-canary.17 (npm)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

See it in your environment

Remediation advice

Upgrade the following packages to resolve this vulnerability:

next to 14.2.34 or later; next to 15.0.6 or later; next to 15.1.10 or later; next to 15.2.7 or later; next to 15.3.7 or later; next to 15.4.9 or later; next to 15.5.8 or later; next to 15.6.0-canary.59 or later; next to 16.0.9 or later; next to 16.1.0-canary.17 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is GHSA-MWV6-3258-Q52C? GHSA-MWV6-3258-Q52C is a high-severity uncontrolled resource consumption vulnerability in next (npm), affecting versions >= 13.3.0, < 14.2.34. It is fixed in 14.2.34, 15.0.6, 15.1.10, 15.2.7, 15.3.7, 15.4.9, 15.5.8, 15.6.0-canary.59, 16.0.9, 16.1.0-canary.17. Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service.
How severe is GHSA-MWV6-3258-Q52C? GHSA-MWV6-3258-Q52C has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of next are affected by GHSA-MWV6-3258-Q52C? next (npm) versions >= 13.3.0, < 14.2.34 is affected.
Is there a fix for GHSA-MWV6-3258-Q52C? Yes. GHSA-MWV6-3258-Q52C is fixed in 14.2.34, 15.0.6, 15.1.10, 15.2.7, 15.3.7, 15.4.9, 15.5.8, 15.6.0-canary.59, 16.0.9, 16.1.0-canary.17. Upgrade to this version or later.
Is GHSA-MWV6-3258-Q52C exploitable, and should I be worried? Whether GHSA-MWV6-3258-Q52C is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether GHSA-MWV6-3258-Q52C is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix GHSA-MWV6-3258-Q52C?
- Upgrade next to 14.2.34 or later
- Upgrade next to 15.0.6 or later
- Upgrade next to 15.1.10 or later
- Upgrade next to 15.2.7 or later
- Upgrade next to 15.3.7 or later
- Upgrade next to 15.4.9 or later
- Upgrade next to 15.5.8 or later
- Upgrade next to 15.6.0-canary.59 or later
- Upgrade next to 16.0.9 or later
- Upgrade next to 16.1.0-canary.17 or later

Other vulnerabilities in next

CVE-IDSeverityPackage summary

CVE-2026-45109Highnext: Next.js has a Middleware / Proxy bypass in App Router applications via segment-prefetch routes -…CVE-2026-44572Lownext: Next.js's Middleware / Proxy redirects can be cache-poisoned CVE-2026-44581Mediumnext: Next.js vulnerable to cross-site scripting in App Router applications using CSP nonces CVE-2026-44582Lownext: Next.js vulnerable to cache poisoning via collisions in React Server Component cache-busting CVE-2026-44580Mediumnext: Next.js has cross-site scripting in beforeInteractive scripts with untrusted input