What is GHSA-H25M-26QC-WCJF?

GHSA-H25M-26QC-WCJF is a high-severity uncontrolled resource consumption vulnerability in next (npm), affecting versions >= 13.0.0, < 15.0.8. It is fixed in 15.0.8, 15.1.12, 15.2.9, 15.3.9, 15.4.11, 15.5.10, 15.6.0-canary.61, 16.0.11, 16.1.5. Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service.

How severe is GHSA-H25M-26QC-WCJF?

GHSA-H25M-26QC-WCJF 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-H25M-26QC-WCJF?

next (npm) versions >= 13.0.0, < 15.0.8 is affected.

Is GHSA-H25M-26QC-WCJF exploitable, and should I be worried?

Whether GHSA-H25M-26QC-WCJF 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-H25M-26QC-WCJF 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-H25M-26QC-WCJF in next | Intelligent Application Security

Q: How severe is GHSA-H25M-26QC-WCJF?

GHSA-H25M-26QC-WCJF 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-H25M-26QC-WCJF?

next (npm) versions >= 13.0.0, < 15.0.8 is affected.

Q: Is there a fix for GHSA-H25M-26QC-WCJF?

Yes. GHSA-H25M-26QC-WCJF is fixed in 15.0.8, 15.1.12, 15.2.9, 15.3.9, 15.4.11, 15.5.10, 15.6.0-canary.61, 16.0.11, 16.1.5. Upgrade to this version or later.

Q: Is GHSA-H25M-26QC-WCJF exploitable, and should I be worried?

Whether GHSA-H25M-26QC-WCJF 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-H25M-26QC-WCJF 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-H25M-26QC-WCJF?

Upgrade: next to 15.0.8 or later, next to 15.1.12 or later, next to 15.2.9 or later, next to 15.3.9 or later, next to 15.4.11 or later, next to 15.5.10 or later, next to 15.6.0-canary.61 or later, next to 16.0.11 or later, next to 16.1.5 or later.

Summary

A vulnerability affects certain React Server Components packages for versions 19.0.x, 19.1.x, and 19.2.x and frameworks that use the affected packages, including Next.js 13.x, 14.x, 15.x, and 16.x using the App Router. The issue is tracked upstream as CVE-2026-23864.

A specially crafted HTTP request can be sent to any App Router Server Function endpoint that, when deserialized, may trigger excessive CPU usage, out-of-memory exceptions, or server crashes. 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-H25M-26QC-WCJF 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 (15.0.8, 15.1.12, 15.2.9, 15.3.9, 15.4.11, 15.5.10, 15.6.0-canary.61, 16.0.11, 16.1.5); upgrading removes the vulnerable code path.

Affected versions

next (>= 13.0.0, < 15.0.8) next (>= 15.1.1-canary.0, < 15.1.12) next (>= 15.2.0-canary.0, < 15.2.9) next (>= 15.3.0-canary.0, < 15.3.9) next (>= 15.4.0-canary.0, < 15.4.11) next (>= 15.5.1-canary.0, < 15.5.10) next (>= 15.6.0-canary.0, < 15.6.0-canary.61) next (>= 16.0.0-beta.0, < 16.0.11) next (>= 16.1.0-canary.0, < 16.1.5)

Security releases

next → 15.0.8 (npm) next → 15.1.12 (npm) next → 15.2.9 (npm) next → 15.3.9 (npm) next → 15.4.11 (npm) next → 15.5.10 (npm) next → 15.6.0-canary.61 (npm) next → 16.0.11 (npm) next → 16.1.5 (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 15.0.8 or later; next to 15.1.12 or later; next to 15.2.9 or later; next to 15.3.9 or later; next to 15.4.11 or later; next to 15.5.10 or later; next to 15.6.0-canary.61 or later; next to 16.0.11 or later; next to 16.1.5 or later

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

Frequently Asked Questions

What is GHSA-H25M-26QC-WCJF? GHSA-H25M-26QC-WCJF is a high-severity uncontrolled resource consumption vulnerability in next (npm), affecting versions >= 13.0.0, < 15.0.8. It is fixed in 15.0.8, 15.1.12, 15.2.9, 15.3.9, 15.4.11, 15.5.10, 15.6.0-canary.61, 16.0.11, 16.1.5. Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service.
How severe is GHSA-H25M-26QC-WCJF? GHSA-H25M-26QC-WCJF 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-H25M-26QC-WCJF? next (npm) versions >= 13.0.0, < 15.0.8 is affected.
Is there a fix for GHSA-H25M-26QC-WCJF? Yes. GHSA-H25M-26QC-WCJF is fixed in 15.0.8, 15.1.12, 15.2.9, 15.3.9, 15.4.11, 15.5.10, 15.6.0-canary.61, 16.0.11, 16.1.5. Upgrade to this version or later.
Is GHSA-H25M-26QC-WCJF exploitable, and should I be worried? Whether GHSA-H25M-26QC-WCJF 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-H25M-26QC-WCJF 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-H25M-26QC-WCJF?
- Upgrade next to 15.0.8 or later
- Upgrade next to 15.1.12 or later
- Upgrade next to 15.2.9 or later
- Upgrade next to 15.3.9 or later
- Upgrade next to 15.4.11 or later
- Upgrade next to 15.5.10 or later
- Upgrade next to 15.6.0-canary.61 or later
- Upgrade next to 16.0.11 or later
- Upgrade next to 16.1.5 or later

Other vulnerabilities in next

CVE-2026-45109 CVE-2026-44572 CVE-2026-44581 CVE-2026-44582 CVE-2026-44580