A flaw was found in libssh. A malicious username expanded through %r in ProxyCommand handling can inject shell metacharacters, exposing environment variables and causing unintended shell behavior.
CVE-2026-59846
Score 3.9 from GitHub Security Advisory (severity: LOW) published 2026-07-21. a secondary CVSS source baseline 3.9; 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.9
- EG Score
- 3.9(high)
- EG Risk
- 18(Track)EG Risk 18/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 computedSeverity39% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS
- 1.8%
- KEV
- Not listed
Published
July 21, 2026
Last Modified
July 23, 2026
References (3)
- secalert@redhathttps://access.redhat.com/errata/RHSA-2026:42922
- secalert@redhathttps://access.redhat.com/security/cve/CVE-2026-59846
- secalert@redhathttps://bugzilla.redhat.com/show_bug.cgi?id=2498179
Vendor Advisories for CVE-2026-59846(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 10× in last 7d / 10× 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 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 14:51 UTCEG score recompute
- 2026-07-21 13:13 UTCEG score recompute
- 2026-07-21 13:12 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-77
- CVE-2016-15057EG 9.9CRITICAL
- CVE-2014-5470EG 9.8EPSS 95%CRITICAL
- CVE-2013-2513EG 9.8CRITICAL
- CVE-2015-20108EG 9.8CRITICAL
- CVE-2015-10096NVD 5.0EG 9.8MEDIUM
- CVE-2017-20156NVD 5.5EG 9.8MEDIUM
- CVE-2016-20017EG 9.8 KEVEPSS 99%CRITICAL
- CVE-2016-4991EG 9.8CRITICAL
- CVE-2015-20107NVD 7.6EG 9.8EPSS 94%HIGH
- CVE-2014-4982EG 9.8EPSS 91%CRITICAL
Frequently asked(5)
What is CVE-2026-59846?
When was CVE-2026-59846 disclosed?
Is CVE-2026-59846 actively exploited?
What is the CVSS score of CVE-2026-59846?
How do I remediate CVE-2026-59846?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-59846
Is Your Infrastructure Affected by CVE-2026-59846?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.