CVE-2026-646486.0MediumCWE-524

CVE-2026-64648: Next.js: Response Body Cache Confusion for Requests Containing Bodies

vercel · next.js

Affected: vercel next.js · Exploitation: unlikely (under 1%)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

0.4%probability of exploitation in the next 30 days

31st percentile

050100

Higher than 31% of scored CVEs

6.0MediumCVSS 4.0

LowMediumHighCrit.

DescriptionCVE.org

Next.js is a React framework for building full-stack web applications. In versions 12.0.0 through 15.5.20 and 16.0.0 through 16.2.10, 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. A safe request would be: fetch(new Request(init), init). An unsafe request would be: fetch(new Request(init), aDifferentInit). This issue has been fixed in versions 15.5.21 and 16.2.11.

Affected products1

From the CVE record. A product or version that is not listed is unknown, not unaffected.

vercel · next.js>= 13.0.0, < 15.5.21; >= 16.0.0, < 16.2.11

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas

Exploitation: Unlikely (under 1%). EPSS under 1%, or no score yet.
CISA KEV: Not listed
Public check: No public nuclei template
Weakness: Use of Cache Containing Sensitive Information · Information Disclosure
Vendor: vercel
Published: July 2026
Band: Unlikely (under 1%), July 2026

CoverageNo articles yet

No CyberSIXT article names CVE-2026-64648 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.