CVE-2026-64647
MEDIUMNext.js: Response Body Cache Confusion with Invalid UTF-8 Request Bodies
Title source: cnaDescription
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 is only an issue when receiving request bodies with a content type charset other than UTF-8. For example, the UTF-16 byte sequences for 삃삃 and 섄섄 in the request body would share the same cache. This issue has been fixed in versions 15.5.21 and 16.2.11.
References (5)
Core 5
Core References
X_Refsource_Confirm x_refsource_confirm
https://github.com/vercel/next.js/security/advisories/GHSA-4633-3j49-mh5q
X_Refsource_Misc x_refsource_misc
https://github.com/vercel/next.js/pull/96008
X_Refsource_Misc x_refsource_misc
https://github.com/vercel/next.js/commit/025bf4a5f7b47fb7758c4ebf1c931a61c451c082
X_Refsource_Misc x_refsource_misc
https://github.com/vercel/next.js/releases/tag/v15.5.21
X_Refsource_Misc x_refsource_misc
https://github.com/vercel/next.js/releases/tag/v16.2.11
Scores
CVSS v3
5.4
EPSS
0.0034
EPSS Percentile
26.4%
Attack Vector
NETWORK
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N
CISA SSVC
Vulnrichment
Exploitation
none
Automatable
no
Technical Impact
partial
Details
CWE
CWE-116
Status
published
Products (3)
vercel/next.js
13.0.0 - 15.5.21
vercel/next.js
>= 13.0.0, < 15.5.21
vercel/next.js
>= 16.0.0, < 16.2.11
Published
Jul 27, 2026
Tracked Since
Jul 28, 2026