CVE-2026-56850

MEDIUMNVD 4.44.4
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 4.4 under NVD CVSS v3. EPSS exploit probability: 0.1% (1st percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 4.1 is lower than this score; a lower GitHub score revises it only when its advisory is newer than the CVE record's last change, and this advisory (published 2026-07-30) is not newer than that change (2026-10-23), so it does not.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3

Also known asEUVD-2026-51020 (ENISA EUVD) · GHSA-777r-4cwx-g26v (GitHub Security Advisories)Source: ENISA EUVD

4.4EG
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.1%CVSS: 4.4Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

A flaw in Node.js HTTPS Agent connection reuse can cause PFX object-array key collisions, allowing mutual TLS (mTLS) client identities to be reused across requests configured with different client certificates. This vulnerability affects Node.js 26.x, 24.x, and 22.x.

CVSS v3
4.4
EG Score
4.4MEDIUMmedium confidence
EG Risk
20
EG Risk 20/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)
Severity44% × 45%
Impact severity (EG Severity): CVSS 4.4 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation<0.1% × 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.1%
EPSS %ILE
1st
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.4): severity, escalated by confirmed exploitation. This CVE's 4.4 is its impact severity (EG Severity), not escalated.

EG Severity
4.4 MEDIUMCVSS-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.1% 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 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

July 30, 2026

Last Modified

October 23, 2026

Advisory Details (1)

Auto-updated Jul 30, 2026
Patch available.
Web page

Node.js — Wednesday, July 29, 2026 Security Releases

https://nodejs.org/en/blog/vulnerability/july-2026-security-releases

Vendor Advisories for CVE-2026-56850(14)

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

Patch Availability(11)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatnodejs22-1:22.23.2-1.el10_02026-09-08redhat
redhatnodejs:22-9060020260901085634.rhel92026-09-02redhat
redhatnodejs:24-8100020260819113942.6d8804032026-09-02redhat
redhatnodejs:22-8100020260819113925.6d8804032026-09-01redhat
redhatnodejs:22-9080020260819113937.rhel92026-08-31redhat
redhatnodejs:24-9080020260819113946.rhel92026-08-31redhat
redhatnodejs22-1:22.23.2-1.el10_22026-08-31redhat
redhatnodejs24-1:24.19.0-1.el10_22026-08-31redhat
redhatnodejs24-main-24.18.1-0.1.hum12026-07-30redhat
redhatnodejs22-main-22.23.2-2.3.hum12026-07-29redhat
redhatnodejs26-main-26.5.1-1.5.hum12026-07-29redhat

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

(9 across 8 ecosystems)
Alpine:v3.24(2)
PackageVulnerable rangeFix by version rangeDependents
nodejs—
  • every version up to 24.18.1-r0: fixed in 24.18.1-r0
—
nodejs-current—
  • every version up to 26.5.1-r0: fixed in 26.5.1-r0
—
Alpine:v3.21(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs—
  • every version up to 22.23.2-r0: fixed in 22.23.2-r0
—
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs—
  • every version up to 22.23.2-r0: fixed in 22.23.2-r0
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs—
  • every version up to 24.18.1-r0: fixed in 24.18.1-r0
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs12.21.0~dfsg-5 ... 24.18.0+dfsg+~cs24.13.2-1 (174 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs18.13.0+dfsg1-1 ... 18.20.4+dfsg-1~deb12u2 (22 versions)
  • every version up to 18.20.4+dfsg-1~deb12u3: fixed in 18.20.4+dfsg-1~deb12u3
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs20.19.2+dfsg-1, 20.19.2+dfsg-1+deb13u1, 20.19.2+dfsg-1+deb13u2
  • every version up to 20.19.2+dfsg-1+deb13u3: fixed in 20.19.2+dfsg-1+deb13u3
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs20.19.2+dfsg-1 ... 24.18.0+dfsg+~cs24.13.2-1 (40 versions)
  • every version up to 24.19.0+dfsg+~cs24.13.3-1: fixed in 24.19.0+dfsg+~cs24.13.3-1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 6× in last 7d / 24× 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 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). "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.

Showing the most recent 100 of 241 rows 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 141 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

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

Frequently asked(5)

What is CVE-2026-56850?
CVE-2026-56850 is a medium-severity vulnerability; its CVE record was published on July 30, 2026. A flaw in Node.js HTTPS Agent connection reuse can cause PFX object-array key collisions, allowing mutual TLS (mTLS) client identities to be reused across requests configured with different client certificates. This vulnerability affects Node.js 26.x, 24.x, and 22.x.
When was the CVE record for CVE-2026-56850 published?
The CVE record for CVE-2026-56850 was published on July 30, 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 23, 2026; the record at its source may have been updated since.
Is CVE-2026-56850 actively exploited?
CVE-2026-56850 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-56850?
CVE-2026-56850 has a CVSS v3 base score of 4.4 (NVD).
How do I remediate CVE-2026-56850?
A fix for CVE-2026-56850 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-56850 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-56850

Explore →

Is Your Infrastructure Affected by CVE-2026-56850?

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

Book a Demo →Browse All CVEs