CVEPublished 2026-07-27Modified 2026-07-290 articles on news4 live referencesNVD data

CVE-2026-64647Vercel · Next.js

Vulnerability data via NVD (ingested)

CVSS v3.1
5.4
MEDIUM
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N
EPSS percentile
41
Exploit Prediction Scoring System · top 59% of all CVEs
Description

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.

Timeline
Published 2026-07-27
Modified 2026-07-29

External references

Search for exposed instances

Shodan + Censys queries derived from NVD's CPE data. The vuln tag catches assets Shodan has explicitly linked to this CVE; the product / banner fingerprints find exposed instances even when the vuln tag was never applied (which is common).

More intel sources (5)

Known PoCs on GitHub

No public proof-of-concept repositories found for CVE-2026-64647 on GitHub.
We haven't classified any articles referencing CVE-2026-64647 yet. The external references above still apply.