CVE-2026-64644 vercel CVE debrief

Who should care

Developers and administrators using Next.js versions 15.5.0 through 15.5.20 and 16.0.0 through 16.2.10 should be aware of this vulnerability and take steps to defend against it. They should review and restrict config.images.remotePatterns, monitor /_next/image endpoints for unusual activity, and implement compensating controls to prevent CPU exhaustion.

Technical summary

The vulnerability is caused by the Image Optimization API's ability to optimize remotely hosted images if configured. If those images contain malicious content, they can cause CPU exhaustion in /_next/image endpoints. The vulnerability only affects config.images.remotePatterns and not config.images.unoptimized: true, config.images.loader: 'custom', and Vercel. The issue has been addressed in versions 15.5.21 and 16.2.11.

Defensive priority

Medium

Recommended defensive actions

• Update Next.js to version 15.5.21 or 16.2.11
• Review and restrict config.images.remotePatterns
• Monitor /_next/image endpoints for unusual activity
• Implement compensating controls to prevent CPU exhaustion
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• Track exceptions, retest remediated assets, and close the item only after evidence is documented

Evidence notes

The CVE record was published on 2026-07-27T18:16:59.307Z and has not been modified since then. The NVD entry is currently 6.3, MEDIUM. The vulnerability affects Next.js versions 15.5.0 through 15.5.20 and 16.0.0 through 16.2.10. The issue has been fixed in versions 15.5.21 and 16.2.11. Evidence limits suggest that defenders verify the configuration of config.images.remotePatterns and review /_next/image endpoints for unusual activity.

Official resources