GHSA-68g3-v927-f742

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

En bref

Publiée
Mise à jour
CVE
CVE-2026-64648
CVSS_V4
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N

Description

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

Paquets affectés

PaquetVersions
npm · nextintroduced 13.0.0, fixed 15.5.21
npm · nextintroduced 16.0.0, fixed 16.2.11

Références

Sources

SourceLicence
OSV.devCC-BY 4.0 — GitHub Advisory Database