Back to CVE records
Medium 5.4Published Jul 27, 2026

CVE-2026-64648Next.js is a React framework for building full-stack web applications.

Updated under an hour ago ()

Does this affect you?

It affects vercel next.js. Add what you run to find out whether that includes you.

No exploitation reported and no EPSS estimate yet.

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.

CVSS
5.4 MEDIUM (v3.1, NVD)CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N
Weakness (CWE)
CWE-524
Known exploited
Not in CISA's KEV catalog
EPSS (exploitation in the next 30 days)
Not loaded for this CVE
Assigned by
Not given
NVD analysis
Analyzed
Record last updated
Jul 29, 2026
First seen by InfoSec Signals
Oct 9, 2026

Affected products

Affected products
vercel next.js
vercel:next.js
from 12.0.0 before 15.5.21; from 16.0.0 before 16.2.11
NVD

References

  • patch
  • patch
  • product, release-notes
  • product, release-notes
  • vendor-advisory

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.

Your cookie choices
We use essential cookies to run this site, and, only with your consent, an advertising cookie from Google to measure whether our ads lead to sign-ups and subscriptions. See our for details.