๐Ÿ” CVE Alert

CVE-2026-64647

UNKNOWN 0.0

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

CVSS Score
0.0
EPSS Score
0.0%
EPSS Percentile
0th

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.

CWE CWE-116
Vendor vercel
Product next.js
Published Jul 27, 2026
Last Updated Jul 27, 2026
Stay Ahead of the Next One

Get instant alerts for vercel next.js

Be the first to know when new unknown vulnerabilities affecting vercel next.js are published โ€” delivered to Slack, Telegram or Discord.

Get Free Alerts โ†’ Free ยท No credit card ยท 60 sec setup

Affected Versions

vercel / next.js
>= 13.0.0, < 15.5.21 >= 16.0.0, < 16.2.11

References

NVD โ†— CVE.org โ†— EPSS Data โ†—
github.com: https://github.com/vercel/next.js/security/advisories/GHSA-4633-3j49-mh5q github.com: https://github.com/vercel/next.js/pull/96008 github.com: https://github.com/vercel/next.js/commit/025bf4a5f7b47fb7758c4ebf1c931a61c451c082 github.com: https://github.com/vercel/next.js/releases/tag/v15.5.21 github.com: https://github.com/vercel/next.js/releases/tag/v16.2.11