libssh2 through 1.11.1, fixed in commit a13bb6c, contains a missing bounds check vulnerability that allows a malicious SSH server to trigger an arbitrary-length heap out-of-bounds read and a free of an uninitialized pointer via the publickey subsystem. In libssh2_publickey_list_fetch(), the version 1 response parser reads a server-controlled comment_len value and advances the parse pointer without verifying sufficient bytes remain in the buffer, causing the out-of-bounds read to leak heap pointers from adjacent allocations defeating ASLR, followed by heap allocator state corruption when the error cleanup path frees an uninitialized pointer from a non-zeroed realloc() region.
CVE-2026-66034
This high-severity CVE scores 7.5 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.5
- EG Score
- 7.5(low)
- EG Risk
- 38(Track)EG Risk 38/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 computedSeverity75% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS
- —
- KEV
- Not listed
Published
July 24, 2026
Last Modified
July 24, 2026
Advisory Details (3)
Auto-updated Jul 24, 2026libssh2 Heap Out-of-Bounds Read via publickey subsystem | Advisories | VulnCheck
https://www.vulncheck.com/advisories/libssh2-heap-out-of-bounds-read-via-publickey-subsystemcommit a13bb6c773f0 (libssh2/libssh2)
Fix landed in libssh2/libssh2 commit a13bb6c773f0 — awaiting tagged release
https://github.com/libssh2/libssh2/commit/a13bb6c773f0d55ad1628cede57e99803cd898d9publickey: fix potential OOB read in `libssh2_publickey_list_fetch()`
Upstream fix in progress (PR #2202 · libssh2/libssh2, state=closed)
https://github.com/libssh2/libssh2/pull/2202Vendor Advisories for CVE-2026-66034(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 2× in last 7d / 2× 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-24 16:53 UTCEG score recompute
- 2026-07-24 16:52 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-125 · CWE-908
- CVE-2014-2896EG 9.8CRITICAL
- CVE-1999-0006EG 9.8EPSS 96%CRITICAL
- CVE-2014-1508EG 9.1EPSS 90%CRITICAL
- CVE-2014-0160NVD 7.5EG 9.0 KEVEPSS 100%HIGH
- CVE-2014-1497EG 8.8HIGH
- CVE-2011-3406EG 8.8EPSS 98%HIGH
- CVE-2008-3475EG 8.8EPSS 98%HIGH
- CVE-2008-4197EG 8.8EPSS 93%HIGH
- CVE-2008-2934EG 8.8HIGH
- CVE-1999-0029EG 8.4HIGH
Frequently asked(4)
What is CVE-2026-66034?
When was CVE-2026-66034 disclosed?
What is the CVSS score of CVE-2026-66034?
How do I remediate CVE-2026-66034?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-66034
Is Your Infrastructure Affected by CVE-2026-66034?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.