~ / search / GHSA-68g3-v927-f742

GHSA-68g3-v927-f742

Next.js: Cache confusion of response bodies for requests with bodies

Source: GitHub Advisory Database (reviewed) Moderate CVE-2026-64648

Packages

EcosystemPackageAffectedFixed in
npm next >= 13.0.0, < 15.5.21 15.5.21
npm next >= 16.0.0, < 16.2.11 16.2.11

Details

As written in the advisory (Markdown source, shown as plain text).

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

References

External links from the advisory. They lead to third-party sites.