vercel · Next.js · published 2026-07-27
CVE-2026-64648Next.js: Response Body Cache Confusion for Requests Containing Bodies
Routine No exploitation evidence; EPSS 0.4%.
CVE-2026-64648 is not known to be exploited in the wild. EPSS estimates a 0.4% chance of exploitation in the next 30 days, higher than 32% of all CVEs. This Next.js vulnerability: CVSS 6.0 (v4.0). Fixed upstream in Next.js 16.2.11, 15.5.21. Routine: patch when convenient.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
Fixed upstream in Next.js 16.2.11, 15.5.21.
Patch events
Web frameworkNext.js
Next.js security releases: 16.2.11, 15.5.21
Upgrade to
16.2.1115.5.21Why: Vendor security release for server software (most severe: CVE-2026-64642).
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | No | CISA KEV |
| Ransomware use | — | CISA KEV |
| EPSS (30-day exploitation probability) | 0.4% (32th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 6.0 (v4.0)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 | CNA / CISA ADP |
| SSVC exploitation | none | CISA Vulnrichment |
| SSVC automatable | No | CISA Vulnrichment |
| SSVC technical impact | partial | CISA Vulnrichment |
Affected versions (from the CVE record)#
- vercel next.js
>= 13.0.0, < 15.5.21(affected)>= 16.0.0, < 16.2.11(affected)
Description (from the CVE record)#
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.
Quoted from the CVE Program record.