CVE-2026-64648

Summary

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

Severity

medium

EPSS

0.3% (p27)

CWE

CWE-524

Also known as

GHSA-68g3-v927-f742

Published

2026-07-22

Updated

2026-07-22

Advisory details

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

• https://github.com/advisories/GHSA-68g3-v927-f742
• https://github.com/vercel/next.js/security/advisories/GHSA-68g3-v927-f742
• https://github.com/vercel/next.js/commit/062f66700b52a5d6bba2c0605d55577ab7ad262c
• https://github.com/vercel/next.js/commit/73b94872bc343d09494b50394d8c08eb9fc8e56a
• https://github.com/vercel/next.js/releases/tag/v15.5.21
• https://github.com/vercel/next.js/releases/tag/v16.2.11

Related advisories

• CVE-2026-103004 — medium · npm/next
• CVE-2026-94544 — medium · npm/next
• CVE-2026-94543 — medium · npm/next
• CVE-2026-94484 — medium · npm/next
• GHSA-673q-mjm6-r5xr — critical · npm/next
• GHSA-2464-fhr4-w9xw — critical · npm/next
• GHSA-vcvr-r3jv-pc5j — critical · npm/next
• GHSA-2xp9-vwfh-vxw4 — critical · npm/next

Is your project exposed to this? Stateward checks every dependency on every pull request and flags it only if your code actually reaches it.

Summarize with AI

ChatGPTClaudePerplexity