Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2026-103004: Next.js versions from 16.3.0 to 16.3.7 warm `use cache` handlers using `next/root-params` and can leak their r

28
Routine
MEDIUM 5.3REMOTEUPGRADE

CVE-2026-103004 is a medium-severity flaw (CVSS 5.3) affecting next.js. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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 enc

Why this priority

  • Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score5.3 (Medium)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionNone
EPSS exploit chance0.2% (top 84%)
CISA exploited listNo
WeaknessCWE-524
Published2026-10-01
Last modified2026-10-05
Publisher (CNA): GitHub, Inc. · Vendor: vercel

Share: LinkedIn · X · Reddit

Last updated 2026-10-05 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

vercel next.js UPGRADE
Affected: >= 16.3.0 and < 16.3.8
Fixed in: 16.3.8
Safe to downgrade to: a release before 16.3.0
1. Check installed version
npm ls next.js
2. UPGRADE to 16.3.8
npm install next.js@">=16.3.8"
3. If no update is available yet, DOWNGRADE to a release before 16.3.0
npm view next.js versions npm install next.js@"<16.3.0"
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-103004?

next.js: upgrade to 16.3.8. Exact commands for each OS are on this page.

Is CVE-2026-103004 being exploited?

CVE-2026-103004 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-103004 affect?

CVE-2026-103004 affects next.js. Severity is medium (CVSS 5.3). 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 tha

How urgent is CVE-2026-103004?

Priority 28/100. Remotely exploitable, no login, no user action

Software pages

Next.js vulnerabilities

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.