CVE-2026-119790 json
Information disclosure across root params in Next.js when a 'use cache' function is called through unstable_cache()
published 2026-11-03 5 d ago modified 2026-11-06 2 d ago also GHSA-mfr8-8qww-v76h
Unreviewed: the maintainers' own advisory
Published by the maintainers on their GitHub repository vercel/next.js. GitHub has not reviewed it into the GitHub Advisory Database and no CVE record has reached us yet, so everything here comes from the maintainers alone. Read the full advisory on GitHub.
- cvss
- 6.3
- version 4.0, the maintainers
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no EPSS score yet
- public exploits
- 0
- none known
Summary
Security advisory published by the maintainers of vercel/next.js for next: the maintainers' own advisory, not a reviewed GitHub Advisory Database entry. The full advisory is on GitHub.
Patch / fix
- npm next 16.4.5
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| the maintainers | 4.0 | 6.3 | 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 |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | next | >=16.3.0, <=16.4.4 |
16.4.5 |
Classification
- Technology feeds
References
Sources
- Maintainer advisory GHSA-mfr8-8qww-v76h
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
The maintainers of vercel/next.js published their own advisory on GitHub. Its facts and headline are shown here; the description stays on GitHub.