CVE-2026-64647
Next.js: Response Body Cache Confusion with Invalid UTF-8 Request Bodies
Reported by github_m · Published July 27, 2026
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.
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| langfuse-fips-2 | Chainguard | 2.95.12-r38 |
| homepage | Chainguard | 1.13.2-r9 |
| jitsucom-jitsu | Wolfi | 2.11.0-r30 |
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| vercel | next.js | >= 13.0.0, < 15.5.21, >= 16.0.0, < 16.2.11 |
| chainguard | langfuse-fips-2 | 0 |
| chainguard | homepage | 0 |
| wolfi | jitsucom-jitsu | 0 |
| vercel | next.js | 16.0.0, 13.0.0 |
| chainguard | langfuse-2 | 0 |
| chainguard | jitsucom-jitsu | 0 |
| chainguard | keep | 0 |
| chainguard | keep-fips | 0 |
| chainguard | langfuse-3 | 0, 0 |
| npm | next | 16.0.0, 13.0.0 |
| chainguard | langfuse-fips-3 | 0 |
| chainguard | cadence-web | 0 |
| chainguard | peerdb-ui | 0 |
| wolfi | langfuse-3 | 0, 0 |
Timeline
- Jul 21, 2026 CVE Published
- Jul 27, 2026 CVE Updated
- Jul 28, 2026 Coalition ESS Score
- Jul 28, 2026 Security Advisory
- Aug 7, 2026 EPSS Score (30 in total, the first dated here)
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2026-64647
vulnetix vdb fixes CVE-2026-64647
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2026-64647/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart
References
- https://github.com/vercel/next.js/security/advisories/GHSA-4633-3j49-mh5q x_refsource_CONFIRM
- https://github.com/vercel/next.js/pull/96008 x_refsource_MISC
- https://github.com/vercel/next.js/commit/025bf4a5f7b47fb7758c4ebf1c931a61c451c082 x_refsource_MISC
- https://github.com/vercel/next.js/releases/tag/v15.5.21 x_refsource_MISC
- https://github.com/vercel/next.js/releases/tag/v16.2.11 x_refsource_MISC
- https://nvd.nist.gov/vuln/detail/CVE-2026-64647 advisory
- https://github.com/advisories/GHSA-4633-3j49-mh5q advisory