CVE-2026-59850

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 72% 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
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: None knownExposed: 0

A fix is available — apply it.

A flaw was found in libssh. If data packets are processed after a channel is closed, channel data callbacks can be invoked after the associated data has already been freed, leading to crashes or possible use-after-free conditions.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
34(Track)
EG Risk 34/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
Severity75% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
28%
KEV
Not listed

Published

July 21, 2026

Last Modified

September 1, 2026

Advisory Details (2)

Auto-updated Jul 21, 2026
Patch available. Sources: redhat.
redhat

2498183 – (CVE-2026-59850) CVE-2026-59850 libssh: libssh: use-after-free via data callbacks on closed channels

https://bugzilla.redhat.com/show_bug.cgi?id=2498183
redhat Patch Available

cve-details

https://access.redhat.com/security/cve/CVE-2026-59850

Vendor Advisories for CVE-2026-59850(5)

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

Patch Availability(5)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulibssh-doc (0.11.3-1ubuntu2.1) @ resolute2026-09-11ubuntu
redhatlibssh-0:0.10.4-19.el9_82026-09-01redhat
redhatlibssh-0:0.9.6-17.el8_102026-09-01redhat
redhatlibssh-0:0.12.0-3.el10_22026-08-17redhat
redhatlibssh-main-0.12.1-4.hum12026-07-21redhat

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:11(1)
PackageVulnerable rangeFixed inDependents
libssh0.10.4-1 ... 0.9.8-0+deb11u2 (25 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
libssh0.10.5-2 ... 0.12.2-1 (17 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
libssh0.11.2-1, 0.11.2-1+deb13u1, 0.11.3-10.11.5-0+deb13u1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
libssh0.11.2-1, 0.11.3-1, 0.12.0-1, 0.12.0-2, 0.12.0-30.12.1-1—

Weakness Classification(1)

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

Additional Vendor Advisories

(2)

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 / 132× 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 248 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-59850?
CVE-2026-59850 is a high vulnerability published on July 21, 2026. A flaw was found in libssh. If data packets are processed after a channel is closed, channel data callbacks can be invoked after the associated data has already been freed, leading to crashes or possible use-after-free conditions.
When was CVE-2026-59850 disclosed?
CVE-2026-59850 was first published in the National Vulnerability Database on July 21, 2026, with the most recent update on September 1, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-59850 actively exploited?
CVE-2026-59850 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 72.3% of all scored CVEs.
What is the CVSS score of CVE-2026-59850?
CVE-2026-59850 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-59850?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-59850, 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-59850

Explore →

Is Your Infrastructure Affected by CVE-2026-59850?

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

Start Free Scan →Browse All CVEs