What is GHSA-5J59-XGG2-R9C4?

GHSA-5J59-XGG2-R9C4 is a high-severity uncontrolled resource consumption vulnerability in next (npm), affecting versions >= 13.3.1-canary.0, < 14.2.35. It is fixed in 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. Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service.

How severe is GHSA-5J59-XGG2-R9C4?

GHSA-5J59-XGG2-R9C4 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-5J59-XGG2-R9C4?

next (npm) versions >= 13.3.1-canary.0, < 14.2.35 is affected.

Is GHSA-5J59-XGG2-R9C4 exploitable, and should I be worried?

Whether GHSA-5J59-XGG2-R9C4 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-5J59-XGG2-R9C4 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-5J59-XGG2-R9C4 in next | Intelligent Application Security

Q: How severe is GHSA-5J59-XGG2-R9C4?

GHSA-5J59-XGG2-R9C4 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-5J59-XGG2-R9C4?

next (npm) versions >= 13.3.1-canary.0, < 14.2.35 is affected.

Q: Is there a fix for GHSA-5J59-XGG2-R9C4?

Yes. GHSA-5J59-XGG2-R9C4 is fixed in 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. Upgrade to this version or later.

Q: Is GHSA-5J59-XGG2-R9C4 exploitable, and should I be worried?

Whether GHSA-5J59-XGG2-R9C4 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-5J59-XGG2-R9C4 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-5J59-XGG2-R9C4?

Upgrade: next to 14.2.35 or later, next to 15.0.7 or later, next to 15.1.11 or later, next to 15.2.8 or later, next to 15.3.8 or later, next to 15.4.10 or later, next to 15.5.9 or later, next to 15.6.0-canary.60 or later, next to 16.0.10 or later, next to 16.1.0-canary.19 or later.

Summary

It was discovered that the fix for CVE-2025-55184 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.

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.

Impact

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

GHSA-5J59-XGG2-R9C4 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.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); upgrading removes the vulnerable code path.

Affected versions

next (>= 13.3.1-canary.0, < 14.2.35) next (>= 15.0.6, < 15.0.7) next (>= 15.1.10, < 15.1.11) next (>= 15.2.7, < 15.2.8) next (>= 15.3.7, < 15.3.8) next (>= 15.4.9, < 15.4.10) next (>= 15.5.8, < 15.5.9) next (>= 15.6.0-canary.59, < 15.6.0-canary.60) next (>= 16.0.9, < 16.0.10) next (>= 16.1.0-canary.17, < 16.1.0-canary.19)

Security releases

next → 14.2.35 (npm) next → 15.0.7 (npm) next → 15.1.11 (npm) next → 15.2.8 (npm) next → 15.3.8 (npm) next → 15.4.10 (npm) next → 15.5.9 (npm) next → 15.6.0-canary.60 (npm) next → 16.0.10 (npm) next → 16.1.0-canary.19 (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.35 or later; next to 15.0.7 or later; next to 15.1.11 or later; next to 15.2.8 or later; next to 15.3.8 or later; next to 15.4.10 or later; next to 15.5.9 or later; next to 15.6.0-canary.60 or later; next to 16.0.10 or later; next to 16.1.0-canary.19 or later

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

Frequently Asked Questions

What is GHSA-5J59-XGG2-R9C4? GHSA-5J59-XGG2-R9C4 is a high-severity uncontrolled resource consumption vulnerability in next (npm), affecting versions >= 13.3.1-canary.0, < 14.2.35. It is fixed in 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. Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service.
How severe is GHSA-5J59-XGG2-R9C4? GHSA-5J59-XGG2-R9C4 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-5J59-XGG2-R9C4? next (npm) versions >= 13.3.1-canary.0, < 14.2.35 is affected.
Is there a fix for GHSA-5J59-XGG2-R9C4? Yes. GHSA-5J59-XGG2-R9C4 is fixed in 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. Upgrade to this version or later.
Is GHSA-5J59-XGG2-R9C4 exploitable, and should I be worried? Whether GHSA-5J59-XGG2-R9C4 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-5J59-XGG2-R9C4 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-5J59-XGG2-R9C4?
- Upgrade next to 14.2.35 or later
- Upgrade next to 15.0.7 or later
- Upgrade next to 15.1.11 or later
- Upgrade next to 15.2.8 or later
- Upgrade next to 15.3.8 or later
- Upgrade next to 15.4.10 or later
- Upgrade next to 15.5.9 or later
- Upgrade next to 15.6.0-canary.60 or later
- Upgrade next to 16.0.10 or later
- Upgrade next to 16.1.0-canary.19 or later

Other vulnerabilities in next

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