libssh2 through 1.11.1, fixed in commit 5e47761, contains a double-free vulnerability in the sftp_open() function in src/sftp.c that allows a malicious SSH server to corrupt the heap of any authenticated client opening an SFTP session. When a server responds to SSH_FXP_OPEN with SSH_FXP_STATUS containing FX_OK, the response data buffer is freed, and if a subsequent sftp_packet_require() call returns a specific error such as LIBSSH2_ERROR_CHANNEL_PACKET_EXCEEDED, the same pointer is freed a second time, enabling tcache dup conditions on glibc systems that allow overlapping allocations and function pointer overwrites.
CVE-2026-66032
This high-severity CVE scores 8.8 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
- 8.8
- EG Score
- 8.8(low)
- EG Risk
- 44(Track)EG Risk 44/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%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 Double-Free Heap Corruption via sftp_open() | Advisories | VulnCheck
https://www.vulncheck.com/advisories/libssh2-double-free-heap-corruption-via-sftp-openPrevent dangling pointer by nullifying data
Fix merged in libssh2/libssh2 PR #2180 on 2026-07-02 — awaiting tagged release
https://github.com/libssh2/libssh2/pull/2180commit 5e4776146552 (libssh2/libssh2)
Fix landed in libssh2/libssh2 commit 5e4776146552 — awaiting tagged release
https://github.com/libssh2/libssh2/commit/5e4776146552d898b9c0e1b313cd093fa8dc92d0Vendor Advisories for CVE-2026-66032(1)
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 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-415
- CVE-2018-0101EG 10.0EPSS 100%CRITICAL
- CVE-2007-4773EG 9.8CRITICAL
- CVE-2018-20996EG 9.8CRITICAL
- CVE-2018-20991EG 9.8CRITICAL
- CVE-2018-20961EG 9.8EPSS 93%CRITICAL
- CVE-2018-3985EG 9.8CRITICAL
- CVE-2018-18751EG 9.8EPSS 90%CRITICAL
- CVE-2018-17825EG 9.8CRITICAL
- CVE-2018-16402EG 9.8CRITICAL
- CVE-2016-8619NVD 5.3EG 9.8EPSS 91%MEDIUM
Frequently asked(4)
What is CVE-2026-66032?
When was CVE-2026-66032 disclosed?
What is the CVSS score of CVE-2026-66032?
How do I remediate CVE-2026-66032?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-66032
Is Your Infrastructure Affected by CVE-2026-66032?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.