A flaw was found in libssh. The API function ssh_get_hexa() is vulnerable to a denial of service when processing zero-length input. This can be exploited remotely by an attacker during GSSAPI (Generic Security Service Application Program Interface) authentication if the server's logging verbosity is set to SSH_LOG_PACKET (3) or higher. Successful exploitation could lead to a self-Denial of Service of the per-connection daemon process.
CVE-2026-0966
This high-severity CVE scores 8.2 under NVD CVSS v3. EPSS exploit probability: 0.6%, top 55% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 8.2
- EG Score
- 8.2(medium)
- EG Risk
- 52(Track)EG Risk 52/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 computedSeverity82% × 45%Exploitation1% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 1%
- EPSS %ILE
- 45%
- KEV
- Not listed
Published
March 26, 2026
Last Modified
August 21, 2026
Advisory Details (4)
Auto-updated Apr 30, 2026libssh 0.12.0 and 0.11.4 security releases – libssh
https://www.libssh.org/2026/02/10/libssh-0-12-0-and-0-11-4-security-releases/2433121 – (CVE-2026-0966) CVE-2026-0966 libssh: Buffer underflow in ssh_get_hexa() on invalid input
https://bugzilla.redhat.com/show_bug.cgi?id=2433121Vendor Advisories for CVE-2026-0966(5)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
- CVE-2026-0966Microsoft Security Response Center (MSRC)Medium
Libssh: buffer underflow in ssh_get_hexa() on invalid input
- RHSA-2026:18683Red Hat Product SecurityMedium
Red Hat Security Advisory: libssh security update
- RHSA-2026:18160Red Hat Product SecurityMedium
Red Hat Security Advisory: libssh security update
- RHSA-2026:7067Red Hat Product SecurityMedium
Red Hat Security Advisory: Red Hat Hardened Images RPMs bug fix and enhancement update
- GHSA-wcqf-w94x-4wg2GitHub Security AdvisoriesMedium
The API function `ssh_get_hexa()` is vulnerable, when 0-lenght input is provided to this function...
Patch Availability(5)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| ubuntu | libssh-doc (0.11.2-1ubuntu0.2) @ questing | 2026-08-21 | ubuntu |
| ubuntu | libssh-gcrypt-dev (0.8.0~20170825.94fa1e38-1ubuntu0.7+esm6) @ bionic | 2026-08-21 | ubuntu |
| redhat | libssh-0:0.12.0-2.el10 | 2026-05-19 | redhat |
| redhat | libssh-0:0.10.4-18.el9 | 2026-05-19 | redhat |
| redhat | libssh-main-0.12.0-1.1.hum1 | 2026-04-08 | 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
(4 across 4 ecosystems)
Debian:11(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| libssh | 0.10.4-1 ... 0.9.8-0+deb11u2 (25 versions) | — | — |
Debian:12(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| libssh | 0.10.5-2 ... 0.12.2-1 (17 versions) | — | — |
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| libssh | 0.11.2-1, 0.11.2-1+deb13u1, 0.11.3-1 | 0.11.5-0+deb13u1 | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| libssh | 0.11.2-1, 0.11.3-1 | 0.12.0-1 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Additional Vendor Advisories
(2)
Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.
Data Freshness Timeline
(refreshed 10× in last 7d / 75× 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 189 total refreshes for this CVE.
- 2026-08-25 13:48 UTCEPSS rescore
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-21 23:48 UTCEPSS rescore
- 2026-08-21 12:20 UTCVendor advisory
- 2026-08-21 12:20 UTCGHSA enrichment
- 2026-08-21 12:15 UTCEG score recompute
- 2026-08-21 12:15 UTCVendor advisory
- 2026-08-21 12:15 UTCGHSA enrichment
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-19 17:03 UTCEPSS rescore
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 10:05 UTCEG score recompute
- 2026-08-16 10:05 UTCVendor advisory
- 2026-08-16 10:05 UTCGHSA enrichment
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 19:26 UTCVendor advisory
- 2026-08-14 19:26 UTCGHSA enrichment
- 2026-08-14 06:24 UTCEG score recompute
- 2026-08-14 06:24 UTCVendor advisory
- 2026-08-14 06:24 UTCGHSA enrichment
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-12 20:41 UTCEG score recompute
- 2026-08-12 20:41 UTCVendor advisory
Show 75 moreShow fewer
- 2026-08-12 20:41 UTCGHSA enrichment
- 2026-08-12 13:50 UTCEPSS rescore
- 2026-08-11 20:48 UTCEG score recompute
- 2026-08-11 20:48 UTCVendor advisory
- 2026-08-11 20:48 UTCGHSA enrichment
- 2026-08-11 13:42 UTCEPSS rescore
- 2026-08-11 03:50 UTCEG score recompute
- 2026-08-11 03:50 UTCVendor advisory
- 2026-08-11 03:50 UTCGHSA enrichment
- 2026-08-10 23:59 UTCEPSS rescore
- 2026-08-10 04:21 UTCVendor advisory
- 2026-08-10 04:21 UTCGHSA enrichment
- 2026-08-09 17:06 UTCEG score recompute
- 2026-08-09 17:06 UTCVendor advisory
- 2026-08-09 17:06 UTCGHSA enrichment
- 2026-08-09 13:46 UTCEPSS rescore
- 2026-08-09 05:57 UTCEG score recompute
- 2026-08-09 05:57 UTCVendor advisory
- 2026-08-09 05:57 UTCGHSA enrichment
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-08 03:31 UTCEG score recompute
- 2026-08-08 03:31 UTCVendor advisory
- 2026-08-08 03:31 UTCGHSA enrichment
- 2026-08-07 16:22 UTCVendor advisory
- 2026-08-07 16:22 UTCGHSA enrichment
- 2026-08-06 18:45 UTCEG score recompute
- 2026-08-06 18:45 UTCVendor advisory
- 2026-08-06 18:45 UTCGHSA enrichment
- 2026-08-06 13:46 UTCEPSS rescore
- 2026-08-06 00:50 UTCEG score recompute
- 2026-08-06 00:50 UTCVendor advisory
- 2026-08-06 00:50 UTCGHSA enrichment
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-04 15:09 UTCEPSS rescore
- 2026-08-04 10:38 UTCEPSS rescore
- 2026-08-03 23:16 UTCEG score recompute
- 2026-08-03 23:16 UTCVendor advisory
- 2026-08-03 23:16 UTCGHSA enrichment
- 2026-08-03 10:35 UTCEPSS rescore
- 2026-08-03 02:32 UTCVendor advisory
- 2026-08-03 02:32 UTCGHSA enrichment
- 2026-08-02 15:21 UTCEG score recompute
- 2026-08-02 15:21 UTCVendor advisory
- 2026-08-02 15:21 UTCGHSA enrichment
- 2026-08-02 02:26 UTCEPSS rescore
- 2026-08-01 04:15 UTCEPSS rescore
- 2026-07-30 16:27 UTCEPSS rescore
- 2026-07-30 01:30 UTCEPSS rescore
- 2026-07-28 15:36 UTCEPSS rescore
- 2026-07-27 14:13 UTCEPSS rescore
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-25 14:17 UTCEPSS rescore
- 2026-07-24 14:17 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 03:04 UTCEG score recompute▲ 1.70
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:24 UTCEPSS rescore
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 14:30 UTCEPSS rescore
- 2026-07-19 02:28 UTCEPSS rescore
- 2026-07-18 10:04 UTCEPSS rescore
- 2026-07-17 05:24 UTCOSV refresh
- 2026-07-16 17:02 UTCEPSS rescore
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-13 22:30 UTCEPSS rescore
- 2026-07-13 06:12 UTCEPSS rescore
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-08 15:15 UTCEPSS rescore
- 2026-07-08 15:15 UTCEPSS rescore
- 2026-07-07 13:46 UTCEPSS rescore
- 2026-07-06 16:27 UTCEPSS rescore
Frequently asked(5)
What is CVE-2026-0966?
When was CVE-2026-0966 disclosed?
Is CVE-2026-0966 actively exploited?
What is the CVSS score of CVE-2026-0966?
How do I remediate CVE-2026-0966?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-0966
Is Your Infrastructure Affected by CVE-2026-0966?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.