CVE-2026-56850

MEDIUMNVD 4.44.4—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 4.4 under NVD CVSS v3. EPSS exploit probability: 0.1%, top 100% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.

Triggered by: NVD CVSS baseline
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
4.4EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 4.4Exploit: None knownExposed: 0

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.4(medium)
EG Risk
20(Track)
EG Risk 20/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity44% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
0%
KEV
Not listed

Published

July 30, 2026

Last Modified

August 25, 2026

Advisory Details (1)

Auto-updated Jul 30, 2026
No patch confirmed yet.
generic

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

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

Vendor Advisories for CVE-2026-56850(4)

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

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
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

(8 across 8 ecosystems)
Alpine:v3.21(1)
PackageVulnerable rangeFixed inDependents
nodejs—22.23.2-r0—
Alpine:v3.22(1)
PackageVulnerable rangeFixed inDependents
nodejs—22.23.2-r0—
Alpine:v3.23(1)
PackageVulnerable rangeFixed inDependents
nodejs—24.18.1-r0—
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
nodejs—24.18.1-r0—
Debian:11(1)
PackageVulnerable rangeFixed inDependents
nodejs12.21.0~dfsg-5 ... 24.18.0+dfsg+~cs24.13.2-1 (174 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
nodejs18.13.0+dfsg1-1 ... 24.20.0+dfsg+~cs24.13.3-2 (90 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
nodejs20.19.2+dfsg-1 ... 24.20.0+dfsg+~cs24.13.3-2 (45 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
nodejs20.19.2+dfsg-1 ... 24.18.0+dfsg+~cs24.13.2-1 (40 versions)24.19.0+dfsg+~cs24.13.3-1—

Weakness Classification(1)

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

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 22× in last 7d / 90× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 157 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-56850?
CVE-2026-56850 is a medium vulnerability 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 CVE-2026-56850 disclosed?
CVE-2026-56850 was first published in the National Vulnerability Database on July 30, 2026, with the most recent update on August 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-56850 actively exploited?
CVE-2026-56850 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 99.7% of all 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?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-56850, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

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.

Start Free Scan →Browse All CVEs