All reports
Medium

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

Affected versions

Affected versions
>= 16.0.0, < 16.2.11
Fixed version
16.2.11
Affected versions
>= 13.0.0, < 15.5.21
Fixed version
15.5.21
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported

Exploitation

CVE-2026-64648

Probability of exploitation in the next 30 days: 0.37%

FIRST EPSS · 2026-11-18

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.

Links

Credits

  • rafabd1