Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1336 CNY

100%
Buy Us a Coffee

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

Quick assessment

Affected
vercel next.js
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.

Next.js 是一个用于构建全栈 Web 应用的 React 框架。在版本 12.0.0 至 15.5.20，以及 16.0.0 至 16.2.10 中，存在一个安全漏洞：当使用带有请求体（request body）发起服务端获取（server-side fetch）时，可能会返回与同一 URL 但不同请求体相关的其他请求的缓存响应体。这会导致原本应包含在 POST 请求响应体中的机密数据泄露给未授权的请求。需要注意的是，请求本身不会被去重（deduped）。 该问题仅在与请求体一起使用的字符集编码不是 UTF-

CVSS 6.3 · Medium EPSS 0.35% · P29

Possible ATT&CK Techniques 1 AI

T1530 · Data from Cloud Storage

Affected Version Matrix 2

VendorProduct Version RangeStatus
vercel next.js >= 13.0.0, < 15.5.21 affected
>= 16.0.0, < 16.2.11 affected
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2026-64647

Vulnerability Information
Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
Next.js: Response Body Cache Confusion with Invalid UTF-8 Request Bodies
Source: CVE Program / CVE List V5
Vulnerability 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.
Source: CVE Program / CVE List V5
CVSS Information
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
Source: CVE Program / CVE List V5
Vulnerability Type
对输出编码和转义不恰当
Source: CVE Program / CVE List V5

Affected Products

Vendor Product Affected Versions CPE Subscribe
vercel next.js >= 13.0.0, < 15.5.21 -

II. Public POCs for CVE-2026-64647

# POC Description Source Link Shenlong Link
AI-Generated POC Premium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2026-64647

请登录查看更多情报信息。

Patches & Fixes for CVE-2026-64647 (2)

Vendor Advisories for CVE-2026-64647 (1)

Vendor Pages for CVE-2026-64647 (1)

Same Patch Batch · vercel · 2026-07-27 · 9 CVEs total

CVE-2026-64642 8.3 HIGH Next.js: Middleware / Proxy bypass in App Router applications using Turbopack and single l
CVE-2026-64645 8.3 HIGH Next.js: Server-Side Request Forgery in rewrites via attacker-controlled destination hostn
CVE-2026-64649 8.3 HIGH Next.js: Server-Side Request Forgery in Server Actions on Custom Servers
CVE-2026-64641 8.2 HIGH Next.js: Denial of Service in App Router using Server Actions
CVE-2026-64643 6.3 MEDIUM Next.js: Unauthenticated Disclosure of Internal Server Function endpoints
CVE-2026-64644 6.3 MEDIUM Next.js: Denial of Service in the Image Optimization API using SVGs
CVE-2026-64646 6.3 MEDIUM Next.js: Unbounded Server Action payload in Edge runtime
CVE-2026-64648 6.0 MEDIUM Next.js: Response Body Cache Confusion for Requests Containing Bodies

IV. Related Vulnerabilities

Same product: next.js
Same vendor: vercel
Same weakness: CWE-116

V. Comments for CVE-2026-64647

No comments yet

Leave a comment