A flaw was found in libssh. On servers with GSSAPIKeyExchange enabled, the gssapi-keyex path does not verify whether the authenticated Kerberos principal is authorized for the requested local user, allowing authenticated clients to log in as arbitrary users.
CVE-2026-59851
Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-07-21. a secondary CVSS source baseline 8.8; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 8.8
- EG Score
- 8.8(medium)
- EG Risk
- 40(Track)EG Risk 40/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 computedSeverity88% × 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
August 17, 2026
Advisory Details (2)
Auto-updated Jul 21, 20262498184 – (CVE-2026-59851) CVE-2026-59851 libssh: libssh: authentication bypass via missing GSSAPI principal check
https://bugzilla.redhat.com/show_bug.cgi?id=2498184Vendor Advisories for CVE-2026-59851(3)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
- RHSA-2026:55855Red Hat Product SecurityHigh
Red Hat Security Advisory: libssh security update
- RHSA-2026:42922Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat Hardened Images RPMs bug fix and enhancement update
- GHSA-x5cr-v39m-53gwGitHub Security AdvisoriesHigh
A flaw was found in libssh. On servers with GSSAPIKeyExchange enabled, the gssapi-keyex path does...
Patch Availability(2)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| redhat | libssh-0:0.12.0-3.el10_2 | 2026-08-17 | redhat |
| 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.
Affected Packages
(1 across 1 ecosystem)
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| libssh | 0.11.2-1, 0.11.3-1, 0.12.0-1, 0.12.0-2, 0.12.0-3 | 0.12.1-1 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 22× in last 7d / 127× 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.
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-11 09:06 UTCEG score recompute
- 2026-09-11 09:06 UTCVendor advisory
- 2026-09-11 09:06 UTCGHSA enrichment
- 2026-09-10 09:35 UTCEPSS rescore
- 2026-09-09 11:33 UTCEG score recompute
- 2026-09-09 11:33 UTCVendor advisory
- 2026-09-09 11:33 UTCGHSA enrichment
- 2026-09-08 22:01 UTCEPSS rescore
- 2026-09-07 22:39 UTCEG score recompute
- 2026-09-07 22:39 UTCVendor advisory
- 2026-09-07 22:39 UTCGHSA enrichment
- 2026-09-07 16:01 UTCEPSS rescore
- 2026-09-06 13:47 UTCEPSS rescore
- 2026-09-06 11:00 UTCVendor advisory
- 2026-09-06 11:00 UTCGHSA enrichment
- 2026-09-05 21:25 UTCEG score recompute
- 2026-09-05 21:25 UTCVendor advisory
- 2026-09-05 21:25 UTCGHSA enrichment
- 2026-09-05 08:58 UTCEG score recompute
- 2026-09-05 08:58 UTCVendor advisory
- 2026-09-05 08:58 UTCGHSA enrichment
- 2026-09-04 05:07 UTCEPSS rescore
- 2026-09-02 14:12 UTCEPSS rescore
- 2026-09-02 00:58 UTCEG score recompute
Show 75 moreShow fewer
- 2026-09-02 00:58 UTCVendor advisory
- 2026-09-02 00:58 UTCGHSA enrichment
- 2026-09-01 13:54 UTCEPSS rescore
- 2026-09-01 04:40 UTCEPSS rescore
- 2026-08-31 03:50 UTCEG score recompute
- 2026-08-31 03:50 UTCVendor advisory
- 2026-08-31 03:50 UTCGHSA enrichment
- 2026-08-30 19:17 UTCEPSS rescore
- 2026-08-30 15:22 UTCVendor advisory
- 2026-08-30 15:22 UTCGHSA enrichment
- 2026-08-30 02:18 UTCEG score recompute
- 2026-08-30 02:18 UTCVendor advisory
- 2026-08-30 02:18 UTCGHSA enrichment
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-28 21:42 UTCEPSS rescore
- 2026-08-27 23:49 UTCEG score recompute
- 2026-08-27 23:49 UTCVendor advisory
- 2026-08-27 23:49 UTCGHSA enrichment
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-27 11:22 UTCVendor advisory
- 2026-08-27 11:21 UTCGHSA enrichment
- 2026-08-26 21:31 UTCEG score recompute
- 2026-08-26 21:31 UTCVendor advisory
- 2026-08-26 21:30 UTCGHSA enrichment
- 2026-08-26 14:46 UTCEPSS rescore
- 2026-08-26 08:27 UTCVendor advisory
- 2026-08-26 08:27 UTCGHSA enrichment
- 2026-08-25 19:59 UTCEG score recompute
- 2026-08-25 19:59 UTCVendor advisory
- 2026-08-25 19:59 UTCGHSA enrichment
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-25 07:20 UTCVendor advisory
- 2026-08-25 07:20 UTCGHSA enrichment
- 2026-08-24 18:50 UTCEG score recompute
- 2026-08-24 18:50 UTCVendor advisory
- 2026-08-24 18:50 UTCGHSA enrichment
- 2026-08-24 06:19 UTCVendor advisory
- 2026-08-24 06:19 UTCGHSA enrichment
- 2026-08-23 17:36 UTCVendor advisory
- 2026-08-23 17:36 UTCGHSA enrichment
- 2026-08-23 05:09 UTCEG score recompute
- 2026-08-23 05:09 UTCVendor advisory
- 2026-08-23 05:09 UTCGHSA enrichment
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-22 16:40 UTCVendor advisory
- 2026-08-22 16:40 UTCGHSA enrichment
- 2026-08-22 03:58 UTCEG score recompute
- 2026-08-22 03:58 UTCVendor advisory
- 2026-08-22 03:58 UTCGHSA enrichment
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-21 15:30 UTCVendor advisory
- 2026-08-21 15:30 UTCGHSA enrichment
- 2026-08-21 03:02 UTCEG score recompute
- 2026-08-21 03:02 UTCVendor advisory
- 2026-08-21 03:02 UTCGHSA enrichment
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-20 14:34 UTCVendor advisory
- 2026-08-20 14:34 UTCGHSA enrichment
- 2026-08-20 00:16 UTCEG score recompute
- 2026-08-20 00:16 UTCVendor advisory
- 2026-08-20 00:16 UTCGHSA enrichment
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-19 11:48 UTCVendor advisory
- 2026-08-19 11:47 UTCGHSA enrichment
- 2026-08-18 23:20 UTCEG score recompute
- 2026-08-18 23:20 UTCVendor advisory
- 2026-08-18 23:20 UTCGHSA enrichment
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-18 10:52 UTCVendor advisory
- 2026-08-18 10:52 UTCGHSA enrichment
- 2026-08-17 22:24 UTCVendor advisory
- 2026-08-17 22:24 UTCGHSA enrichment
- 2026-08-17 21:38 UTCEG score recompute
- 2026-08-17 21:38 UTCVendor advisory
- 2026-08-17 21:37 UTCGHSA enrichment
Frequently asked(5)
What is CVE-2026-59851?
When was CVE-2026-59851 disclosed?
Is CVE-2026-59851 actively exploited?
What is the CVSS score of CVE-2026-59851?
How do I remediate CVE-2026-59851?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-59851
Is Your Infrastructure Affected by CVE-2026-59851?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.