CVE-2026-64648: Next.js: Cache confusion of response bodies for requests with bodies
A server-side fetch with a request body may return a cached response body from a different request to the same URL but different body. Confidential data in the POST’s response body would then leak to unauthorized requests. Though the request itself will not be deduped.
This only applies to fetch calls with a request that has a different init than the one passed to fetch.
Safe: fetch(new Request(init), init)
Unsafe: fetch(new Request(init), aDifferentInit)
References
- github.com/advisories/GHSA-68g3-v927-f742
- github.com/vercel/next.js/commit/062f66700b52a5d6bba2c0605d55577ab7ad262c
- github.com/vercel/next.js/commit/73b94872bc343d09494b50394d8c08eb9fc8e56a
- github.com/vercel/next.js/releases/tag/v15.5.21
- github.com/vercel/next.js/releases/tag/v16.2.11
- github.com/vercel/next.js/security/advisories/GHSA-68g3-v927-f742
- nvd.nist.gov/vuln/detail/CVE-2026-64648
Code Behaviors & Features
Detect and mitigate CVE-2026-64648 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →