NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · npm

CVE-2026-64647: Next.js: Cache confusion of response bodies for requests with bodies containing invalid UTF-8 byte sequences

mediumCVSS 4.0 6.3GHSA-4633-3j49-mh5q

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

Published Jul 22, 2026

Affected packages

next

Ecosystem
npm
Affected
>= 13.0.0, < 15.5.21
Fixed in
15.5.21
Check
npm ls next

next

Ecosystem
npm
Affected
>= 16.0.0, < 16.2.11
Fixed in
16.2.11
Check
npm ls next

Advisory details

From the GitHub Advisory Database (CC BY 4.0).

Impact

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.

Workarounds

If you cannot upgrade, consider only making fetch requests with UTF-8 bodies (default in Next.js). Applications using Pages Router are not vulnerable.

Credited to yorukot.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology

More npm vulnerabilities

All npm entries