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.
CVE-2026-59850
Score 4.3 from GitHub Security Advisory published 2026-07-21. a secondary CVSS source baseline 4.3; sources differ by 0.0.
- Lower severity and no public exploit yet
A fix is available — apply it.
- CVSS v3
- 4.3
- EG Score
- 4.3(high)
- EG Risk
- 19(Track)EG Risk 19/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 computedSeverity43% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 21%
- KEV
- Not listed
Published
July 21, 2026
Last Modified
July 22, 2026
Advisory Details (2)
Auto-updated Jul 21, 20262498183 – (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=2498183Vendor Advisories for CVE-2026-59850(2)
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 / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| redhat | libssh-main-0.12.1-4.hum1 | 2026-07-21 | redhat |
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.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 26× in last 7d / 26× 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.
- 2026-07-27 08:14 UTCEG score recompute
- 2026-07-27 08:14 UTCVendor advisory
- 2026-07-27 08:14 UTCGHSA enrichment
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 10:32 UTCEG score recompute
- 2026-07-26 10:32 UTCVendor advisory
- 2026-07-26 10:32 UTCGHSA enrichment
- 2026-07-25 14:18 UTCEPSS rescore
- 2026-07-25 14:18 UTCEPSS rescore
- 2026-07-24 14:18 UTCEPSS rescore
- 2026-07-24 14:18 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 03:21 UTCEG score recompute
- 2026-07-22 23:09 UTCEG score recompute
- 2026-07-22 23:09 UTCGHSA enrichment
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 17:23 UTCEG score recompute
- 2026-07-21 17:23 UTCGHSA enrichment
- 2026-07-21 16:04 UTCEG score recompute
- 2026-07-21 16:04 UTCGHSA enrichment
- 2026-07-21 15:29 UTCEG score recompute
- 2026-07-21 14:39 UTCEG score recompute
Show 1 moreShow fewer
- 2026-07-21 14:37 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-59850?
When was CVE-2026-59850 disclosed?
Is CVE-2026-59850 actively exploited?
What is the CVSS score of CVE-2026-59850?
How do I remediate CVE-2026-59850?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-59850
Is Your Infrastructure Affected by CVE-2026-59850?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.