PT-2026-63562 · Npm · Next

CVE-2026-64647 · Published 2026-07-22 · Updated 2026-07-22

OSV

CVSS v4.0

6.3

Medium

Base vector

AV:N/AC:H/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N

Impact

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.

Workarounds

If you cannot upgrade, consider only making fetch requests with UTF-8 bodies (default in Next.js). Applications using Pages Router are not vulnerable.

Fix

Improper Encoding or Escaping of Output

Weakness Enumeration

CWE-116

Related Identifiers

CVE-2026-64647

GHSA-4633-3J49-MH5Q

Affected Products

Next

References · 7

• https://osv.dev/vulnerability/GHSA-4633-3j49-mh5q · Vendor Advisory
• https://github.com/vercel/next.js/pull/96008 · Note
• https://github.com/vercel/next.js/releases/tag/v16.2.11 · Note
• https://github.com/vercel/next.js/commit/025bf4a5f7b47fb7758c4ebf1c931a61c451c082 · Note
• https://github.com/vercel/next.js/security/advisories/GHSA-4633-3j49-mh5q · Note
• https://github.com/vercel/next.js · Note
• https://github.com/vercel/next.js/releases/tag/v15.5.21 · Note