GHSA-2XP9-VWFH-VXW4

GHSA-2XP9-VWFH-VXW4 is a critical-severity security vulnerability in next (npm), affecting versions >= 10.0.0, < 15.5.24. It is fixed in 15.5.24, 16.3.3.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

Next.js: Unauthenticated Remote Code Execution in Image Optimization API when AVIF files are used

A vulnerability in the underlying libheif library used by sharp which Next.js uses for image optimization can lead to remote code execution when AVIF files are optimized.

Until a fix has propagated, optimization of AVIF files is disabled.

Impact

Affected versions

next (>= 10.0.0, < 15.5.24) next (>= 16.0.0, < 16.3.3)

Security releases

next → 15.5.24 (npm) next → 16.3.3 (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.

Already deployed Kodem?

See it in your environmentNew to Kodem? Get a demo →

Remediation advice

Upgrade the following packages to resolve this vulnerability:

next to 15.5.24 or later; next to 16.3.3 or later

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

Frequently Asked Questions

  1. What is GHSA-2XP9-VWFH-VXW4? GHSA-2XP9-VWFH-VXW4 is a critical-severity security vulnerability in next (npm), affecting versions >= 10.0.0, < 15.5.24. It is fixed in 15.5.24, 16.3.3.
  2. Which versions of next are affected by GHSA-2XP9-VWFH-VXW4? next (npm) versions >= 10.0.0, < 15.5.24 is affected.
  3. Is there a fix for GHSA-2XP9-VWFH-VXW4? Yes. GHSA-2XP9-VWFH-VXW4 is fixed in 15.5.24, 16.3.3. Upgrade to this version or later.
  4. Is GHSA-2XP9-VWFH-VXW4 exploitable, and should I be worried? Whether GHSA-2XP9-VWFH-VXW4 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
  5. What actually determines whether GHSA-2XP9-VWFH-VXW4 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.
  6. How do I fix GHSA-2XP9-VWFH-VXW4?
    • Upgrade next to 15.5.24 or later
    • Upgrade next to 16.3.3 or later

Stop the waste.
Protect your environment with Kodem.