CVE-2026-64647

MEDIUM

Next.js: Response Body Cache Confusion with Invalid UTF-8 Request Bodies

Title source: cna
STIX 2.1

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 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.

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