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

CVE-2026-64648: Next.js: Cache confusion of response bodies for requests with bodies

mediumCVSS 4.0 6.0GHSA-68g3-v927-f742

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 only applies to fetch calls with a request that has a different init than the one passed to fetch.

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 only applies to fetch calls with a request that has a different init than the one passed to fetch. Safe: fetch(new Request(init), init) Unsafe: fetch(new Request(init), aDifferentInit)

Workarounds

No workaround exists besides upgrading. Applications using Pages Router are not vulnerable.

Credited to rafabd1.

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