A flaw was found in libssh. When ProxyCommand is used, an unchecked fork() failure can be stored as process ID -1; during cleanup, signals may then be sent across the caller's accessible process tree, leading to local denial of service.
CVE-2026-59845
Score 5.3 from GitHub Security Advisory published 2026-07-21. a secondary CVSS source baseline 5.3; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.3
- EG Score
- 5.3(high)
- EG Risk
- 28(Track)EG Risk 28/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 computedSeverity53% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS
- 1.5%
- KEV
- Not listed
Published
July 21, 2026
Last Modified
July 23, 2026
Advisory Details (2)
Auto-updated Jul 21, 20262498178 – (CVE-2026-59845) CVE-2026-59845 libssh: libssh: denial of service via unchecked ProxyCommand fork() failure
https://bugzilla.redhat.com/show_bug.cgi?id=2498178Vendor Advisories for CVE-2026-59845(2)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 13× in last 7d / 13× 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-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:18 UTCEG score recompute
- 2026-07-22 23:18 UTCGHSA enrichment
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 12:34 UTCEG score recompute
- 2026-07-21 12:33 UTCGHSA enrichment
- 2026-07-21 11:35 UTCEG score recompute
- 2026-07-21 11:32 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-390
- CVE-2026-52989EG 9.8CRITICAL
- CVE-2022-22532EG 9.8CRITICAL
- CVE-2021-40391EG 9.8CRITICAL
- CVE-2026-53434EG 9.1CRITICAL
- CVE-2024-30255NVD 5.3EG 9.0EPSS 100%MEDIUM
- CVE-2024-27919NVD 7.5EG 9.0EPSS 100%HIGH
- CVE-2019-5051EG 8.8EPSS 90%HIGH
- CVE-2025-46367EG 7.8HIGH
- CVE-2024-49841EG 7.8HIGH
- CVE-2025-26465EG 6.8EPSS 94%MEDIUM
Frequently asked(5)
What is CVE-2026-59845?
When was CVE-2026-59845 disclosed?
Is CVE-2026-59845 actively exploited?
What is the CVSS score of CVE-2026-59845?
How do I remediate CVE-2026-59845?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-59845
Is Your Infrastructure Affected by CVE-2026-59845?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.