What is CVE-2025-30218?

CVE-2025-30218 is a low-severity security vulnerability in next (npm), affecting versions = 12.3.5. It is fixed in 12.3.6, 13.5.10, 14.2.26, 15.2.4.

Which versions of next are affected by CVE-2025-30218?

next (npm) versions = 12.3.5 is affected.

Is there a fix for CVE-2025-30218?

Yes. CVE-2025-30218 is fixed in 12.3.6, 13.5.10, 14.2.26, 15.2.4. Upgrade to this version or later.

Is CVE-2025-30218 exploitable, and should I be worried?

Whether CVE-2025-30218 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 CVE-2025-30218 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.

CVE-2025-30218 in next | Intelligent Application Security

Q: How do I fix CVE-2025-30218?

Upgrade: next to 12.3.6 or later, next to 13.5.10 or later, next to 14.2.26 or later, next to 15.2.4 or later.

Summary

In the process of remediating CVE-2025-29927, we looked at other possible exploits of Middleware. We independently verified this low severity vulnerability in parallel with two reports from independent researchers.

Learn more here.

Credit

Thank you to Jinseo Kim kjsman and RyotaK (GMO Flatt Security Inc.) with takumi-san.ai for the responsible disclosure. These researchers were awarded as part of our bug bounty program.

Impact

Affected versions

next (= 12.3.5) next (= 13.5.9) next (= 14.2.25) next (= 15.2.3)

Security releases

next → 12.3.6 (npm) next → 13.5.10 (npm) next → 14.2.26 (npm) next → 15.2.4 (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 12.3.6 or later; next to 13.5.10 or later; next to 14.2.26 or later; next to 15.2.4 or later

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

Frequently Asked Questions

What is CVE-2025-30218? CVE-2025-30218 is a low-severity security vulnerability in next (npm), affecting versions = 12.3.5. It is fixed in 12.3.6, 13.5.10, 14.2.26, 15.2.4.
Which versions of next are affected by CVE-2025-30218? next (npm) versions = 12.3.5 is affected.
Is there a fix for CVE-2025-30218? Yes. CVE-2025-30218 is fixed in 12.3.6, 13.5.10, 14.2.26, 15.2.4. Upgrade to this version or later.
Is CVE-2025-30218 exploitable, and should I be worried? Whether CVE-2025-30218 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 CVE-2025-30218 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 CVE-2025-30218?
- Upgrade next to 12.3.6 or later
- Upgrade next to 13.5.10 or later
- Upgrade next to 14.2.26 or later
- Upgrade next to 15.2.4 or later

Other vulnerabilities in next

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