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

Goal: 1000 CNY · Raised: 1359 CNY

100%
Buy Us a Coffee

CVE-2026-103004— next.js cache leak on warm `use cache` handlers accessing root param

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 版本从 16.3.0 到 16.3.7 中，使用 的 处理器在预热（warm）过程中，可能会将其返回值泄露给具有不同根参数（root params）的页面。 当启用缓存组件功能（ ）时，如果一个 函数调用了另一个读取根参数的 函数，且内部调用命中了已存在的缓存条目，则可能导致键（key）生成错误：外层函数的缓存键会遗漏该根参数。由于外层条目仅写入一次，并被所有不同的根参数值复用，因此针对某一特定根参数值的响应可能会返回为另一不同值生成的内容——无论该页面是在构建时预渲染、运行时预渲染，还是动态渲染。

CVSS 6.3 · Medium

Possible ATT&CK Techniques 1 AI

T1567 · Exfiltration Over Web Service
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2026-103004

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 cache leak on warm `use cache` handlers accessing root param
Source: CVE Program / CVE List V5
Vulnerability Description
Next.js versions from 16.3.0 to 16.3.7 warm `use cache` handlers using `next/root-params` and can leak their return value to pages with different root params. With Cache Components enabled (cacheComponents: true), a 'use cache' function that calls another 'use cache' function that reads a root param can be keyed incorrectly when the inner call is served from an existing entry: the enclosing function's cache key then omits that root param. The enclosing entry is written once and reused for all root param values, so a response for one root param value can serve content produced for a different value — whether the page is prerendered at build time or at runtime, or rendered dynamically. Shared cache headers let downstream caches redistribute the content further. What values are leaked cannot be attacker controlled. Which value's content is served depends only on which invocation wrote the entry first. This has been patched in 16.3.8.
Source: CVE Program / CVE List V5
CVSS Information
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/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 < 16.3.8 -

II. Public POCs for CVE-2026-103004

# 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-103004

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

Vendor Advisories for CVE-2026-103004 (1)

Vendor Pages for CVE-2026-103004 (1)

IV. Related Vulnerabilities

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

V. Comments for CVE-2026-103004

No comments yet

Leave a comment