CVE-2026-84961

CRITICALNVD 9.19.1
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.1 under NVD CVSS v3. EPSS exploit probability: 0.2% (7th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Trending — Patch released this week

Also known asEUVD-2026-71494 (ENISA EUVD) · GHSA-w293-vg96-wgc3 (GitHub Security Advisories)Source: ENISA EUVD

9.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 9.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

undici's BalancedPool constructor passes its entire options object through an internal deep-clone that serializes and reparses the value as JSON. Because JSON cannot represent functions, any function-valued TLS option, such as a caller-supplied checkServerIdentity callback or a custom connector inside the connect option, is silently discarded before it reaches the TLS layer. As a result a peer whose certificate the application's custom checkServerIdentity was written to reject, but which still passes Node's default hostname and chain checks, is accepted when reached through BalancedPool. The Client, Pool, and Agent dispatchers are not affected because they extract the connect and tls options before cloning. This affects undici versions from 7.24.1 up to 7.29.1 and from 8.0.0 up to 8.10.2, and only when the application supplies a function-valued connect or tls option to BalancedPool. Users should upgrade to undici 7.29.1 or 8.10.2.

CVSS v3
9.1
EG Score
9.1CRITICALmedium confidence
EG Risk
41
EG Risk 41/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)
Severity91% × 45%
Impact severity (EG Severity): CVSS 9.1 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 low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (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.
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 (9.1): severity, escalated by confirmed exploitation. This CVE's 9.1 is its impact severity (EG Severity), not escalated.

EG Severity
9.1 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-26). 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; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

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

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

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

In CISA KEV no (CISA's KEV catalog) · Automatable no (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

September 4, 2026

Last Modified

September 15, 2026

Advisory Details (2)

Auto-updated Sep 15, 2026
Patch available. Sources: github.
GitHub advisoryMentions a patch (unverified)

undici vulnerable to TLS certificate validation bypass via dropped connect options in BalancedPool · Advisory · nodejs/undici · GitHub

https://github.com/nodejs/undici/security/advisories/GHSA-w293-vg96-wgc3
Web page

Security Advisories | OpenJS Foundation CVE Numbering Authority

https://cna.openjsf.org/security-advisories.html

Vendor Advisories for CVE-2026-84961(17)

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

Patch Availability(16)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhoai/odh-workbench-codeserver-datascience-cpu-py312-rhel9:17918254692026-10-21redhat
redhatrhoai/odh-workbench-codeserver-datascience-cpu-py312-rhel9:17912884002026-10-21redhat
redhatrhoai/odh-workbench-codeserver-datascience-cpu-py312-rhel9:17917882672026-10-19redhat
redhatansible-automation-platform/bootc-automation-portal-rhel9:17918656602026-10-13redhat
redhatansible-automation-platform/automation-portal:17912953792026-10-12redhat
redhatansible-automation-platform/automation-portal:17912937802026-10-12redhat
redhatrhdh/rhdh-hub-rhel9:17913114952026-10-08redhat
redhatrhdh/red-hat-developer-hub-backstage-plugin-scaffolder-backend-module-orchestrator:17912496402026-10-06redhat
redhatcluster-observability-operator/monitoring-console-plugin-rhel9:17908545252026-10-01redhat
redhatnodejs:24-8100020260921144227.6d8804032026-09-30redhat
redhatnodejs:24-9080020260921144317.rhel92026-09-30redhat
redhatnodejs24-1:24.21.0-1.el10_22026-09-29redhat
redhatrhdh/rhdh-hub-rhel9:17895542852026-09-21redhat
redhatnodejs26-main-26.8.2-0.1.hum12026-09-11redhat
redhatgrafana12-4-main-12.4.10-0.2.hum12026-09-09redhat
redhatnodejs24-main-24.18.1-0.2.2.hum12026-08-12redhat

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

(4 across 4 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
node-undici5.15.0+dfsg1+~cs20.10.9.3-1 ... 8.9.0+dfsg+~cs3.2.0-1 (40 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
node-undici7.15.0+dfsg+~cs3.2.0-1 ... 8.9.0+dfsg+~cs3.2.0-1 (16 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
node-undici7.15.0+dfsg+~cs3.2.0-1 ... 8.9.0+dfsg+~cs3.2.0-1 (15 versions)
  • every version up to 8.10.2+dfsg+~cs3.2.2-1: fixed in 8.10.2+dfsg+~cs3.2.2-1
—
npm(1)
PackageVulnerable rangeFix by version rangeDependents
undici—
  • 7.24.1 up to 7.29.1: fixed in 7.29.1
  • 8.0.0 up to 8.10.2: fixed in 8.10.2
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 22× in last 7d / 140× 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.

Showing the most recent 100 of 264 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 164 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-27 02:42 UTCEG score recompute
  2. 2026-10-27 02:42 UTCVendor advisory
  3. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  4. 2026-10-25 23:53 UTCEG score recompute
  5. 2026-10-25 23:53 UTCVendor advisory
  6. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  7. 2026-10-25 13:55 UTCEG score recompute
  8. 2026-10-25 01:09 UTCEG score recompute
  9. 2026-10-25 01:09 UTCVendor advisory
  10. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  11. 2026-10-24 02:25 UTCEG score recompute
  12. 2026-10-24 02:25 UTCVendor advisory
  13. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  14. 2026-10-23 03:42 UTCEG score recompute
  15. 2026-10-23 03:42 UTCVendor advisory
  16. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  17. 2026-10-22 04:57 UTCEG score recompute
  18. 2026-10-22 04:57 UTCVendor advisory
  19. 2026-10-21 16:34 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  20. 2026-10-21 06:11 UTCEG score recompute
  21. 2026-10-21 06:11 UTCVendor advisory
  22. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  23. 2026-10-20 07:27 UTCEG score recompute
  24. 2026-10-20 07:27 UTCVendor advisory
  25. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
Show 75 more
  1. 2026-10-19 08:43 UTCEG score recompute
  2. 2026-10-19 08:43 UTCVendor advisory
  3. 2026-10-18 16:33 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  4. 2026-10-18 09:59 UTCVendor advisory
  5. 2026-10-18 03:06 UTCEG score recompute
  6. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  7. 2026-10-17 11:16 UTCEG score recompute
  8. 2026-10-17 11:16 UTCVendor advisory
  9. 2026-10-16 16:44 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  10. 2026-10-16 12:32 UTCEG score recompute
  11. 2026-10-16 12:32 UTCVendor advisory
  12. 2026-10-15 16:33 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  13. 2026-10-15 13:48 UTCEG score recompute
  14. 2026-10-15 13:48 UTCVendor advisory
  15. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  16. 2026-10-14 08:43 UTCEG score recompute
  17. 2026-10-14 08:43 UTCVendor advisory
  18. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  19. 2026-10-13 03:59 UTCEG score recompute
  20. 2026-10-13 03:59 UTCVendor advisory
  21. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  22. 2026-10-12 14:53 UTCEG score recompute
  23. 2026-10-12 05:16 UTCVendor advisory
  24. 2026-10-11 19:18 UTCEG score recompute
  25. 2026-10-11 16:34 UTCEG score recompute
  26. 2026-10-11 13:52 UTCEG score recompute
  27. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  28. 2026-10-10 17:19 UTCVendor advisory
  29. 2026-10-10 13:00 UTCVendor advisory
  30. 2026-10-10 09:02 UTCVendor advisory
  31. 2026-10-10 03:07 UTCVendor advisory
  32. 2026-10-09 23:06 UTCEG score recompute
  33. 2026-10-09 23:06 UTCVendor advisory
  34. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  35. 2026-10-09 05:08 UTCVendor advisory
  36. 2026-10-09 01:10 UTCEG score recompute
  37. 2026-10-09 01:10 UTCVendor advisory
  38. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  39. 2026-10-08 07:07 UTCVendor advisory
  40. 2026-10-08 03:09 UTCEG score recompute
  41. 2026-10-08 03:09 UTCVendor advisory
  42. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  43. 2026-10-07 23:05 UTCVendor advisory
  44. 2026-10-07 07:44 UTCVendor advisory
  45. 2026-10-07 03:46 UTCVendor advisory
  46. 2026-10-06 23:48 UTCVendor advisory
  47. 2026-10-06 19:51 UTCVendor advisory
  48. 2026-10-06 15:52 UTCEG score recompute
  49. 2026-10-06 15:52 UTCVendor advisory
  50. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  51. 2026-10-06 11:10 UTCVendor advisory
  52. 2026-10-06 07:12 UTCVendor advisory
  53. 2026-10-06 02:57 UTCVendor advisory
  54. 2026-10-05 23:00 UTCVendor advisory
  55. 2026-10-05 18:10 UTCEG score recompute
  56. 2026-10-05 18:10 UTCVendor advisory
  57. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  58. 2026-10-05 14:11 UTCVendor advisory
  59. 2026-10-05 10:14 UTCVendor advisory
  60. 2026-10-05 06:16 UTCVendor advisory
  61. 2026-10-05 02:18 UTCEG score recompute
  62. 2026-10-05 02:18 UTCVendor advisory
  63. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  64. 2026-10-04 22:06 UTCVendor advisory
  65. 2026-10-04 18:08 UTCVendor advisory
  66. 2026-10-04 13:16 UTCVendor advisory
  67. 2026-10-04 08:53 UTCVendor advisory
  68. 2026-10-04 04:55 UTCVendor advisory
  69. 2026-10-04 00:56 UTCVendor advisory
  70. 2026-10-03 20:28 UTCVendor advisory
  71. 2026-10-03 16:31 UTCEG score recompute
  72. 2026-10-03 16:31 UTCVendor advisory
  73. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  74. 2026-10-03 12:33 UTCVendor advisory
  75. 2026-10-03 05:54 UTCVendor advisory

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-84961?
CVE-2026-84961 is a critical-severity vulnerability; its CVE record was published on September 4, 2026. undici's BalancedPool constructor passes its entire options object through an internal deep-clone that serializes and reparses the value as JSON. Because JSON cannot represent functions, any function-valued TLS option, such as a caller-supplied checkServerIdentity callback or a custom connector…
When was the CVE record for CVE-2026-84961 published?
The CVE record for CVE-2026-84961 was published on September 4, 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 September 15, 2026; the record at its source may have been updated since.
Is CVE-2026-84961 actively exploited?
CVE-2026-84961 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-84961?
CVE-2026-84961 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2026-84961?
A fix for CVE-2026-84961 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-84961 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-84961

Explore →

Is Your Infrastructure Affected by CVE-2026-84961?

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

Book a Demo →Browse All CVEs