mediumVulnerability

CVE-2026-64648

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

Properties

ghsa_id
GHSA-68g3-v927-f742
severity
medium
summary
Next.js: Cache confusion of response bodies for requests with bodies
epss_score
0.00336
cve_id
CVE-2026-64648
is_ghsa_only
false
ghsa_published
2026-07-22T23:08:17Z
source_url
https://github.com/advisories/GHSA-68g3-v927-f742
epss_percentile
0.26352
ghsa_updated
2026-07-22T23:08:20Z

Related Entities (5)

ENRICHED_BY (1)

[Source]FIRST EPSS

VULNERABLE_TO (1)

[Software]npm/next

AFFECTS (1)

[Software]npm/next

HAS_WEAKNESS (1)

[Weakness]Use of Cache Containing Sensitive Information

REPORTED_BY (1)

[Source]GitHub Advisory Database

Explore deeper with Ninja Signal's threat intelligence graph

CVE-2026-64648 — Ninja Signal Threat Intelligence | Ninja Signal