Vulnerability Description
Next.js is a React framework for building full-stack web applications. In versions 12.0.0 through 15.5.20 and 16.0.0 through 16.2.10, 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. A safe request would be: fetch(new Request(init), init). An unsafe request would be: fetch(new Request(init), aDifferentInit). This issue has been fixed in versions 15.5.21 and 16.2.11.
CVSS Score
MEDIUM
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Vercel | Next.Js | >= 12.0.0, < 15.5.21 |
Related Weaknesses (CWE)
References
- https://github.com/vercel/next.js/commit/062f66700b52a5d6bba2c0605d55577ab7ad262Patch
- https://github.com/vercel/next.js/commit/73b94872bc343d09494b50394d8c08eb9fc8e56Patch
- https://github.com/vercel/next.js/releases/tag/v15.5.21ProductRelease Notes
- https://github.com/vercel/next.js/releases/tag/v16.2.11ProductRelease Notes
- https://github.com/vercel/next.js/security/advisories/GHSA-68g3-v927-f742Vendor Advisory
FAQ
What is CVE-2026-64648?
CVE-2026-64648 is a vulnerability with a CVSS score of 5.4 (MEDIUM). Next.js is a React framework for building full-stack web applications. In versions 12.0.0 through 15.5.20 and 16.0.0 through 16.2.10, a server-side fetch with a request body may return a cached respo...
How severe is CVE-2026-64648?
CVE-2026-64648 has been rated MEDIUM with a CVSS base score of 5.4/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2026-64648?
Check the references section above for vendor advisories and patch information. Affected products include: Vercel Next.Js.