Next.js Affected by Cache Key Confusion for Image Optimization API Routes
GHSA-g5qg-72qw-gw5v · CVE-2025-57752
Published · Modified
AI SAST
Find this class of vulnerability in your own code
Corgea's AI-native static analysis detects vulnerabilities like this one across your repositories, ranks them by exploitability, and returns review-ready fixes.
Description
A vulnerability in Next.js Image Optimization has been fixed in v15.4.5 and v14.2.31. When images returned from API routes vary based on request headers (such as Cookie or Authorization), these responses could be incorrectly cached and served to unauthorized users due to a cache key confusion bug.
All users are encouraged to upgrade if they use API routes to serve images that depend on request headers and have image optimization enabled.
More details at Vercel Changelog
References
- WEB https://github.com/vercel/next.js/security/advisories/GHSA-g5qg-72qw-gw5v
- ADVISORY https://nvd.nist.gov/vuln/detail/CVE-2025-57752
- WEB https://github.com/vercel/next.js/pull/82114
- WEB https://github.com/vercel/next.js/commit/6b12c60c61ee80cb0443ccd20de82ca9b4422ddd
- PACKAGE https://github.com/vercel/next.js
- WEB https://vercel.com/changelog/cve-2025-57752
Ready to move
Start Securing
Free, no credit card | First findings in minutes