CVE-2026-119790

MEDIUMPre-NVD 6.36.3
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This medium-severity CVE scores 6.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (30th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source

Also known asEUVD-2026-126578 (ENISA EUVD) · GHSA-mfr8-8qww-v76h (GitHub Security Advisories)Source: ENISA EUVD

6.3EG
EchelonGraph verdictMonitorRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 6.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Next.js is a React framework for building full-stack web applications. From 16.3.0 until 16.4.5, Next.js applications using the same 'use cache' function directly during rendering and through unstable_cache() can disclose cached data across root params when that function reads a root param. During the first fill after a cold process start, cross-request deduplication allows a concurrent unstable_cache() request to join the direct call's in-flight fill and receive its result before the root param mismatch is rejected. unstable_cache() then persists that result under a key that omits root params, causing later requests for other root param values to receive the same entry until revalidation or eviction. Exploitation requires the unstable_cache() request to arrive while the first fill is in flight. Outside this race, nesting 'use cache' inside unstable_cache() raises an unsupported-operation error, and avoiding that nesting prevents the issue. This issue is fixed in version 16.4.5.

CVSS
6.3
EG Score
6.3MEDIUMmedium confidence
EG Risk
44
EG Risk 44/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity63% × 45%
Impact severity (EG Severity): CVSS 6.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.4%
EPSS %ILE
30th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (6.3): severity, escalated by confirmed exploitation. This CVE's 6.3 is its impact severity (EG Severity), not escalated.

EG Severity
6.3 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS. FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

November 16, 2026

Last Modified

November 18, 2026

Advisory Details (4)

Auto-updated Nov 16, 2026
Patch available. Sources: github, github_commit, github_release.
Web page

November 2026 Security Release | Next.js

https://nextjs.org/blog/november-2026-security-release
GitHub release Patch Available

v16.4.5

Patch available: vercel/next.js v16.4.5

https://github.com/vercel/next.js/releases/tag/v16.4.5
GitHub commit Patch Available

commit d605874e5a4b (vercel/next.js)

Patch available: vercel/next.js v16.4.5 (contains commit d605874e5a4b)

https://github.com/vercel/next.js/commit/d605874e5a4b8b6b7dca1b6e07bcabb44d0e2e5b
GitHub advisoryMentions a patch (unverified)

Information disclosure across root params in Next.js when a 'use cache' function is called through unstable_cache() · Advisory · vercel/next.js · GitHub

https://github.com/vercel/next.js/security/advisories/GHSA-mfr8-8qww-v76h

Vendor Advisories for CVE-2026-119790(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
npmnext @ 16.4.5 (fixes >= 16.3.0, <= 16.4.4)—ghsa

These rows come from GitHub (GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 11× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-21 16:38 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  2. 2026-11-20 16:36 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  3. 2026-11-20 05:18 UTCEchelonGraph re-scored
  4. 2026-11-20 05:18 UTCGHSA enrichmentGHSA-mfr8-8qww-v76h · GitHub severity MODERATE
  5. 2026-11-19 16:33 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  6. 2026-11-18 18:30 UTCEchelonGraph re-scored
  7. 2026-11-18 18:30 UTCGHSA enrichmentGHSA-mfr8-8qww-v76h · GitHub severity MODERATE
  8. 2026-11-18 16:33 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  9. 2026-11-17 16:34 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  10. 2026-11-16 20:52 UTCGHSA enrichmentGHSA-mfr8-8qww-v76h · GitHub severity MODERATE
  11. 2026-11-16 19:38 UTCEchelonGraph re-scored
  12. 2026-11-16 19:38 UTCGHSA enrichmentGHSA-mfr8-8qww-v76h · GitHub severity MODERATE
  13. 2026-11-16 19:03 UTCENISA EUVD ID recordedEUVD-2026-126578 · Source: ENISA EUVD
  14. 2026-11-16 18:21 UTCEchelonGraph re-scoredFirst assessed: 6.3 MEDIUM
  15. 2026-11-16 18:19 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-119790?
CVE-2026-119790 is a medium-severity vulnerability; its CVE record was published on November 16, 2026. Next.js is a React framework for building full-stack web applications. From 16.3.0 until 16.4.5, Next.js applications using the same 'use cache' function directly during rendering and through unstable_cache() can disclose cached data across root params when that function reads a root param. During…
When was the CVE record for CVE-2026-119790 published?
The CVE record for CVE-2026-119790 was published on November 16, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 18, 2026; the record at its source may have been updated since.
Is CVE-2026-119790 actively exploited?
CVE-2026-119790 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (30th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-119790?
CVE-2026-119790 has a CVSS base score of 6.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-119790?
A fix for CVE-2026-119790 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-119790 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-119790

Explore →

Is Your Infrastructure Affected by CVE-2026-119790?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.