Vulnerability in Vercel Next.js

CVE-2026-64648

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.

EPSS: 0.004 (30.5th percentile) — read the EPSS interpretation.

CVSS v3 metric

CVSS v3 base score 5.4 (Medium). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N.

Affected products

  • Vercel Next.js — versions >= 13.0.0, < 15.5.21, >= 16.0.0, < 16.2.11

Weakness classification (CWE)

References

Frequently asked questions

What is CVE-2026-64648?
CVE-2026-64648 is a medium-severity vulnerability in Vercel Next.js, classified under Use of Cache Containing Sensitive Information. CVSS score: 5.4/10. Published 2026-07-27.
How severe is CVE-2026-64648?
Medium severity. CVSS v3 base score is 5.4 out of 10.