A flaw was found in libssh. During server-side GSSAPI key exchange, a client-supplied Curve25519 public key shorter than the expected length is copied without proper length validation, leading to an out-of-bounds heap read. This could allow a remote unauthenticated attacker to disclose small amounts of server memory.
CVE-2026-59842
Score 3.7 from GitHub Security Advisory (severity: LOW) published 2026-07-21. a secondary CVSS source baseline 3.7; 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
- 3.7
- EG Score
- 3.7(high)
- EG Risk
- 17(Track)EG Risk 17/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 computedSeverity37% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS
- 26.6%
- KEV
- Not listed
Published
July 21, 2026
Last Modified
July 22, 2026
References (3)
- secalert@redhathttps://access.redhat.com/errata/RHSA-2026:42922
- secalert@redhathttps://access.redhat.com/security/cve/CVE-2026-59842
- secalert@redhathttps://bugzilla.redhat.com/show_bug.cgi?id=2498168
Vendor Advisories for CVE-2026-59842(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 9× in last 7d / 9× 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-23 03:21 UTCEG score recompute
- 2026-07-22 23:19 UTCEG score recompute
- 2026-07-22 23:19 UTCGHSA enrichment
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 12:58 UTCEG score recompute
- 2026-07-21 12:58 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-125
- CVE-2014-2898EG 9.8CRITICAL
- CVE-2014-2897EG 9.8CRITICAL
- CVE-2014-2896EG 9.8CRITICAL
- CVE-2015-9290EG 9.8CRITICAL
- CVE-2016-10749EG 9.8CRITICAL
- CVE-1999-0006EG 9.8EPSS 96%CRITICAL
- CVE-2014-3180EG 9.1CRITICAL
- CVE-2014-1508EG 9.1EPSS 90%CRITICAL
- CVE-2016-5198NVD 8.8EG 9.0 KEVEPSS 98%HIGH
- CVE-2016-4523NVD 7.5EG 9.0 KEVEPSS 98%HIGH
Frequently asked(5)
What is CVE-2026-59842?
When was CVE-2026-59842 disclosed?
Is CVE-2026-59842 actively exploited?
What is the CVSS score of CVE-2026-59842?
How do I remediate CVE-2026-59842?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-59842
Is Your Infrastructure Affected by CVE-2026-59842?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.