CVE-2026-64648: Next.js: Cache confusion of response bodies for requests with bodies
Impact 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.
Published Jul 22, 2026
Affected packages
next
- Ecosystem
- npm
- Affected
- >= 13.0.0, < 15.5.21
- Fixed in
- 15.5.21
- Check
npm ls next
next
- Ecosystem
- npm
- Affected
- >= 16.0.0, < 16.2.11
- Fixed in
- 16.2.11
- Check
npm ls next
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
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)
Workarounds
No workaround exists besides upgrading. Applications using Pages Router are not vulnerable.
Credited to rafabd1.
References
- https://github.com/vercel/next.js/security/advisories/GHSA-68g3-v927-f742
- https://github.com/vercel/next.js/commit/062f66700b52a5d6bba2c0605d55577ab7ad262c
- https://github.com/vercel/next.js/commit/73b94872bc343d09494b50394d8c08eb9fc8e56a
- https://github.com/vercel/next.js/releases/tag/v15.5.21
- https://github.com/vercel/next.js/releases/tag/v16.2.11
- https://github.com/advisories/GHSA-68g3-v927-f742
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More npm vulnerabilities
All npm entriesCVE-2026-119346
Next.js: HttpOnly cookie exposure through internal response header on Next.js Edge runtime routes
medium6.0Nov 19, 2026CVE-2026-119347
Next.js: SVG rejection bypass in the image optimization
medium6.9Nov 19, 2026CVE-2026-119348
Next.js: Cross-client response injection and disclosure in self-hosted Next.js applications forwarding fetched responses
medium6.3Nov 19, 2026CVE-2026-119349
Next.js: Cross-user cache disclosure and poisoning in Next.js use cache with binary arguments
medium6.3Nov 19, 2026CVE-2026-119350
Next.js: Cache poisoning of shared fallback shells in Cache Components via request-supplied placeholder route params
medium6.3Nov 19, 2026CVE-2026-119351
Next.js: Cache leak across root param values in nested 'use cache' functions via delayed inner stream metadata
medium6.3Nov 17, 2026
