CVE-2026-0966

HIGHNVD 8.28.2—
EchelonGraph scoreMEDIUM confidence

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.

Triggered by: NVD CVSS baseline
Sources: epss, ghsa, nvd
8.2EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 8.2Exploit: None knownExposed: 0

A fix is available — apply it.

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.

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 computed
Severity82% × 45%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
46%
KEV
Not listed

Published

March 26, 2026

Last Modified

September 1, 2026

Advisory Details (4)

Auto-updated Apr 30, 2026
Patch available. Sources: redhat.
generic

libssh 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/
redhat

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=2433121
redhat Patch Available

cve-details

https://access.redhat.com/security/cve/CVE-2026-0966
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:7067

Vendor 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.

Patch Availability(5)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulibssh-gcrypt-dev (0.8.0~20170825.94fa1e38-1ubuntu0.7+esm6) @ bionic2026-09-01ubuntu
ubuntulibssh-doc (0.11.2-1ubuntu0.2) @ questing2026-09-01ubuntu
redhatlibssh-0:0.12.0-2.el102026-05-19redhat
redhatlibssh-0:0.10.4-18.el92026-05-19redhat
redhatlibssh-main-0.12.0-1.1.hum12026-04-08redhat

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)
PackageVulnerable rangeFixed inDependents
libssh0.10.4-1 ... 0.9.8-0+deb11u2 (25 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
libssh0.10.5-2 ... 0.12.2-1 (17 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
libssh0.11.2-1, 0.11.2-1+deb13u1, 0.11.3-10.11.5-0+deb13u1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
libssh0.11.2-1, 0.11.3-10.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 4× in last 7d / 37× 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 217 total refreshes for this CVE.

  1. 2026-09-18 19:27 UTCEPSS rescore
  2. 2026-09-16 05:14 UTCEPSS rescore
  3. 2026-09-13 16:46 UTCEPSS rescore
  4. 2026-09-12 15:00 UTCEPSS rescore
  5. 2026-09-11 14:52 UTCEPSS rescore
  6. 2026-09-11 09:36 UTCEPSS rescore
  7. 2026-09-10 09:34 UTCEPSS rescore
  8. 2026-09-08 22:00 UTCEPSS rescore
  9. 2026-09-07 16:01 UTCEPSS rescore
  10. 2026-09-06 13:47 UTCEPSS rescore
  11. 2026-09-04 05:06 UTCEPSS rescore
  12. 2026-09-02 14:11 UTCEPSS rescore
  13. 2026-09-01 13:53 UTCEPSS rescore
  14. 2026-09-01 12:27 UTCVendor advisory
  15. 2026-09-01 12:27 UTCGHSA enrichment
  16. 2026-09-01 12:02 UTCEG score recompute
  17. 2026-09-01 12:02 UTCVendor advisory
  18. 2026-09-01 12:02 UTCGHSA enrichment
  19. 2026-09-01 04:39 UTCEPSS rescore
  20. 2026-08-31 16:43 UTCVendor advisory
  21. 2026-08-31 16:43 UTCGHSA enrichment
  22. 2026-08-31 15:08 UTCEG score recompute
  23. 2026-08-31 15:08 UTCVendor advisory
  24. 2026-08-31 15:08 UTCGHSA enrichment
  25. 2026-08-30 19:17 UTCEPSS rescore
Show 75 more
  1. 2026-08-30 01:21 UTCEPSS rescore
  2. 2026-08-28 21:40 UTCEPSS rescore
  3. 2026-08-27 14:24 UTCEPSS rescore
  4. 2026-08-25 13:48 UTCEPSS rescore
  5. 2026-08-23 00:19 UTCEPSS rescore
  6. 2026-08-21 23:48 UTCEPSS rescore
  7. 2026-08-21 12:20 UTCVendor advisory
  8. 2026-08-21 12:20 UTCGHSA enrichment
  9. 2026-08-21 12:15 UTCEG score recompute
  10. 2026-08-21 12:15 UTCVendor advisory
  11. 2026-08-21 12:15 UTCGHSA enrichment
  12. 2026-08-20 22:55 UTCEPSS rescore
  13. 2026-08-19 17:03 UTCEPSS rescore
  14. 2026-08-18 13:48 UTCEPSS rescore
  15. 2026-08-16 14:56 UTCEPSS rescore
  16. 2026-08-16 10:05 UTCEG score recompute
  17. 2026-08-16 10:05 UTCVendor advisory
  18. 2026-08-16 10:05 UTCGHSA enrichment
  19. 2026-08-16 02:14 UTCEPSS rescore
  20. 2026-08-15 01:30 UTCEPSS rescore
  21. 2026-08-14 19:26 UTCVendor advisory
  22. 2026-08-14 19:26 UTCGHSA enrichment
  23. 2026-08-14 06:24 UTCEG score recompute
  24. 2026-08-14 06:24 UTCVendor advisory
  25. 2026-08-14 06:24 UTCGHSA enrichment
  26. 2026-08-13 22:00 UTCEPSS rescore
  27. 2026-08-12 20:41 UTCEG score recompute
  28. 2026-08-12 20:41 UTCVendor advisory
  29. 2026-08-12 20:41 UTCGHSA enrichment
  30. 2026-08-12 13:50 UTCEPSS rescore
  31. 2026-08-11 20:48 UTCEG score recompute
  32. 2026-08-11 20:48 UTCVendor advisory
  33. 2026-08-11 20:48 UTCGHSA enrichment
  34. 2026-08-11 13:42 UTCEPSS rescore
  35. 2026-08-11 03:50 UTCEG score recompute
  36. 2026-08-11 03:50 UTCVendor advisory
  37. 2026-08-11 03:50 UTCGHSA enrichment
  38. 2026-08-10 23:59 UTCEPSS rescore
  39. 2026-08-10 04:21 UTCVendor advisory
  40. 2026-08-10 04:21 UTCGHSA enrichment
  41. 2026-08-09 17:06 UTCEG score recompute
  42. 2026-08-09 17:06 UTCVendor advisory
  43. 2026-08-09 17:06 UTCGHSA enrichment
  44. 2026-08-09 13:46 UTCEPSS rescore
  45. 2026-08-09 05:57 UTCEG score recompute
  46. 2026-08-09 05:57 UTCVendor advisory
  47. 2026-08-09 05:57 UTCGHSA enrichment
  48. 2026-08-08 16:37 UTCEPSS rescore
  49. 2026-08-08 03:31 UTCEG score recompute
  50. 2026-08-08 03:31 UTCVendor advisory
  51. 2026-08-08 03:31 UTCGHSA enrichment
  52. 2026-08-07 16:22 UTCVendor advisory
  53. 2026-08-07 16:22 UTCGHSA enrichment
  54. 2026-08-06 18:45 UTCEG score recompute
  55. 2026-08-06 18:45 UTCVendor advisory
  56. 2026-08-06 18:45 UTCGHSA enrichment
  57. 2026-08-06 13:46 UTCEPSS rescore
  58. 2026-08-06 00:50 UTCEG score recompute
  59. 2026-08-06 00:50 UTCVendor advisory
  60. 2026-08-06 00:50 UTCGHSA enrichment
  61. 2026-08-05 19:17 UTCEPSS rescore
  62. 2026-08-04 15:09 UTCEPSS rescore
  63. 2026-08-04 10:38 UTCEPSS rescore
  64. 2026-08-03 23:16 UTCEG score recompute
  65. 2026-08-03 23:16 UTCVendor advisory
  66. 2026-08-03 23:16 UTCGHSA enrichment
  67. 2026-08-03 10:35 UTCEPSS rescore
  68. 2026-08-03 02:32 UTCVendor advisory
  69. 2026-08-03 02:32 UTCGHSA enrichment
  70. 2026-08-02 15:21 UTCEG score recompute
  71. 2026-08-02 15:21 UTCVendor advisory
  72. 2026-08-02 15:21 UTCGHSA enrichment
  73. 2026-08-02 02:26 UTCEPSS rescore
  74. 2026-08-01 04:15 UTCEPSS rescore
  75. 2026-07-30 16:27 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-0966?
CVE-2026-0966 is a high vulnerability published on March 26, 2026. A flaw was found in libssh. The API function sshgethexa() 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…
When was CVE-2026-0966 disclosed?
CVE-2026-0966 was first published in the National Vulnerability Database on March 26, 2026, with the most recent update on September 1, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-0966 actively exploited?
CVE-2026-0966 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 53.5% of all scored CVEs.
What is the CVSS score of CVE-2026-0966?
CVE-2026-0966 has a CVSS v3 base score of 8.2 (NVD).
How do I remediate CVE-2026-0966?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-0966, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-0966

Explore →

Is Your Infrastructure Affected by CVE-2026-0966?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs