ZDF
Sign inSign up

Vulnerabilities

Security incident · CVE-2026-103004

next.js cache leak across root param values in nested 'use cache' functions

Published Oct 1, 2026 · catalog updated Oct 22, 2026 · next.js cache leak across

Last checked Oct 23, 2026. A connected source was read within the last 7 days.

Check if you run it

No confirmed exploitation is on record for CVE-2026-103004. EPSS is 0.25%. Act only if a listed version of next.js cache leak across is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (next.js cache leak across).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.

Same product and reporting

Severity
Medium6.3
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.25%
Remediation
Version ranges on file
Affected products
npm next · vendor vercel next.js

Next.js versions from 16.3.0 to 16.3.7 warm handlers using 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.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • npm next>= 16.3.0, < 16.3.8
  • vendor vercel next.jsversion unspecified

How to fix CVE-2026-103004

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-103004. EPSS is 0.25%. Act only if a listed version of next.js cache leak across is installed.

Which versions are affected?

Compare what you have installed with >= 16.3.0, < 16.3.8. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-524. EPSS 0.25%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Oct 22, 2026 · GitHub Advisory Database

    Detected

    ### Impact With Cache Components enabled ( ), a function that calls another 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 dif

  2. Oct 22, 2026 · GitHub Advisory Database

    Updated

    ### Impact With Cache Components enabled ( ), a function that calls another 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 dif

Sources

  • CVE.orgVulnerability recordCVE-2026-103004

    Next.js versions from 16.3.0 to 16.3.7 warm handlers using 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 key

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2026-103004

    30-day exploitation probability 0.25%

    first.org
  • GitHub Advisory DatabasePackage advisoryGHSA-h694-7cp9-m8p3

    next.js cache leak across root param values in nested 'use cache' functions

    github.com
  • GitLab Advisory DatabasePackage advisoryCVE-2026-103004

    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

    advisories.gitlab.com

References

Freshness

Last verified in this catalog Oct 23, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • GitLab Advisory DatabaseOct 23, 2026
  • FIRST EPSSOct 23, 2026
  • CVE.orgOct 23, 2026
  • GitHub Advisory DatabaseOct 23, 2026