vercel · Next.js · published 2026-07-27

CVE-2026-64647Next.js: Response Body Cache Confusion with Invalid UTF-8 Request Bodies

Routine No exploitation evidence; EPSS 0.4%.

CVE-2026-64647 is not known to be exploited in the wild. EPSS estimates a 0.4% chance of exploitation in the next 30 days, higher than 29% of all CVEs. This Next.js vulnerability: CVSS 6.3 (v4.0). Fixed upstream in Next.js 16.2.11, 15.5.21. Routine: patch when convenient.

Share this

Remediation#

Fixed upstream in Next.js 16.2.11, 15.5.21.

Patch events

  1. This monthSecurity release

    Web frameworkNext.js

    Next.js security releases: 16.2.11, 15.5.21

    Upgrade to 16.2.1115.5.21

    Why: Vendor security release for server software (most severe: CVE-2026-64642).

Exploit intelligence#

SignalValueSource
Known exploitedNoCISA KEV
Ransomware use—CISA KEV
EPSS (30-day exploitation probability)0.4% (30th pct)FIRST EPSS v2026.06.15
CVSS base score6.3 (v4.0)
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N
CNA / CISA ADP
SSVC exploitationnoneCISA Vulnrichment
SSVC automatableNoCISA Vulnrichment
SSVC technical impactpartialCISA Vulnrichment

Affected versions (from the CVE record)#

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 is only an issue when receiving request bodies with a content type charset other than UTF-8. For example, the UTF-16 byte sequences for 삃삃 and 섄섄 in the request body would share the same cache. This issue has been fixed in versions 15.5.21 and 16.2.11.

Quoted from the CVE Program record.

Elsewhere#

Distro status: Debian · Ubuntu · Red Hat · Alpine

Something wrong on this page?
Anonymous. Reports are checked against the primary source.

Also on today's list

See today's list → · Coming up →