CVE-2026-94544

MEDIUMNVD 4.24.2
EchelonGraph scoreHIGH confidence

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

Score 4.2 from GitHub Security Advisory (severity: MODERATE) published 2026-10-07. NVD baseline CVSS 4.2; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this week

Also known asEUVD-2026-91668 (ENISA EUVD) · GHSA-3w37-wq28-93x7 (GitHub Security Advisories)Source: ENISA EUVD

4.2EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 4.2Exploit: 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.3.8, pending use cache fills for the same key are shared without separating Draft Mode requests from regular requests. An overlapping regular request can receive unauthenticated unpublished content from an editor's Draft Mode fill, while an overlapping Draft Mode request can receive published content from a regular fill. When the regular request prerenders a page, the draft-dependent content can persist in the generated page and be served to later visitors until revalidation. Sites are affected when Cache Components or experimental.useCache is enabled and cached functions return draft-dependent content. This issue is fixed in version 16.3.8.

CVSS v3
4.2
EG Score
4.2MEDIUMhigh confidence
EG Risk
19
EG Risk 19/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)
Severity42% × 45%
Impact severity (EG Severity): CVSS 4.2 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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.
EPSS PROB
0.2%
EPSS %ILE
7th
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 (4.2): severity, escalated by confirmed exploitation. This CVE's 4.2 is its impact severity (EG Severity), not escalated.

EG Severity
4.2 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). 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 every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade 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 every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (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

October 2, 2026

Last Modified

October 5, 2026

Advisory Details (3)

Auto-updated Oct 2, 2026
Patch available. Sources: github_release, github, github_commit.
GitHub release Patch Available

v16.3.8

Patch available: vercel/next.js v16.3.8

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

commit bd9214f9a328 (vercel/next.js)

Patch available: vercel/next.js v16.3.8 (contains commit bd9214f9a328)

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

Pending `use cache` fill can leak Draft Mode content into regular responses and persisted pages · Advisory · vercel/next.js · GitHub

https://github.com/vercel/next.js/security/advisories/GHSA-3w37-wq28-93x7

Vendor Advisories for CVE-2026-94544(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.3.8 (fixes >= 16.3.0, < 16.3.8)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
next—
  • 16.3.0 up to 16.3.8: fixed in 16.3.8
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 47× 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 it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 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). Most recent first.

  1. 2026-11-01 16:36 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  2. 2026-11-01 07:37 UTCGHSA enrichmentGHSA-3w37-wq28-93x7 · GitHub severity MODERATE · GitHub CVSS 4.2
  3. 2026-11-01 07:37 UTCEG score recompute
  4. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  5. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  6. 2026-10-29 17:09 UTCEG score recompute
  7. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  8. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  9. 2026-10-27 16:33 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  10. 2026-10-26 16:33 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  11. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  12. 2026-10-25 13:49 UTCEG score recompute
  13. 2026-10-24 16:34 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  14. 2026-10-23 16:33 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  15. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  16. 2026-10-22 12:26 UTCEG score recompute
  17. 2026-10-21 16:34 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  18. 2026-10-20 16:34 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  19. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  20. 2026-10-18 16:33 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  21. 2026-10-18 02:58 UTCEG score recompute
  22. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  23. 2026-10-16 16:45 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  24. 2026-10-14 16:34 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  25. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.2% · 6th percentile
Show 25 more
  1. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  2. 2026-10-12 14:41 UTCEG score recompute
  3. 2026-10-11 19:11 UTCEG score recompute
  4. 2026-10-11 16:27 UTCEG score recompute
  5. 2026-10-11 13:50 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  6. 2026-10-11 13:40 UTCEG score recompute
  7. 2026-10-10 21:54 UTCEG score recompute
  8. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  9. 2026-10-09 21:52 UTCEG score recompute
  10. 2026-10-09 20:08 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  11. 2026-10-08 21:50 UTCEG score recompute
  12. 2026-10-08 17:14 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  13. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  14. 2026-10-06 21:27 UTCEG score recompute
  15. 2026-10-06 15:19 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  16. 2026-10-05 21:13 UTCEG score recompute
  17. 2026-10-05 17:44 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  18. 2026-10-05 15:07 UTCEG score recompute▼ 2.10
  19. 2026-10-05 15:04 UTCNVD updateCVSS v3 → 4.2
  20. 2026-10-04 23:23 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  21. 2026-10-03 18:19 UTCEG score recompute
  22. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  23. 2026-10-02 16:28 UTCEG score recompute
  24. 2026-10-02 15:31 UTCEG score recomputeFirst assessed: 6.3 MEDIUM
  25. 2026-10-02 15:30 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-94544?
CVE-2026-94544 is a medium-severity vulnerability; its CVE record was published on October 2, 2026. Next.js is a React framework for building full-stack web applications. From 16.3.0 until 16.3.8, pending use cache fills for the same key are shared without separating Draft Mode requests from regular requests. An overlapping regular request can receive unauthenticated unpublished content from an…
When was the CVE record for CVE-2026-94544 published?
The CVE record for CVE-2026-94544 was published on October 2, 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 October 5, 2026; the record at its source may have been updated since.
Is CVE-2026-94544 actively exploited?
CVE-2026-94544 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (7th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-94544?
CVE-2026-94544 has a CVSS v3 base score of 4.2 (NVD).
How do I remediate CVE-2026-94544?
A fix for CVE-2026-94544 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-94544 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-94544

Explore →

Is Your Infrastructure Affected by CVE-2026-94544?

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

Book a Demo →Browse All CVEs