CVE-2026-64647

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

State
Published
Severity
6.3 Medium
Published
Jul 27, 2026
Updated
Jul 27, 2026
Reserved
Jul 20, 2026

Read the record on cve.org

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

CVSSScoreVectorSource
4.06.3 MediumCVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:NGitHub_M

Weaknesses

  • CWE-116 Improper Encoding or Escaping of Output

Affected Products

ProductVersions
next.jsvercel
  • >= 13.0.0, < 15.5.21Affected
  • >= 16.0.0, < 16.2.11Affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.