CVE-2026-66032

HIGHPre-NVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-07-24. a secondary CVSS source baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.8Exploit: None knownExposed: 0

A fix is available — apply it.

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.

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 computed
Severity88% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
38%
KEV
Not listed

Published

July 24, 2026

Last Modified

August 7, 2026

Advisory Details (3)

Auto-updated Jul 24, 2026
Upstream fix merged — awaiting tagged release. Sources: github_commit, github_pr.
generic

libssh2 Double-Free Heap Corruption via sftp_open() | Advisories | VulnCheck

https://www.vulncheck.com/advisories/libssh2-double-free-heap-corruption-via-sftp-open
github_pr

Prevent 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/2180
github_commit

commit 5e4776146552 (libssh2/libssh2)

Fix landed in libssh2/libssh2 commit 5e4776146552 — awaiting tagged release

https://github.com/libssh2/libssh2/commit/5e4776146552d898b9c0e1b313cd093fa8dc92d0

Vendor Advisories for CVE-2026-66032(3)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulibssh2-1t64 (1.11.1-1ubuntu0.26.04.4) @ resolute2026-09-15ubuntu
redhatlibssh2-0:1.8.0-4.el7_9.22026-08-31redhat
redhatlibssh2-main-1.11.1-10.2.hum12026-07-27redhat

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
libssh21.10.0-1 ... 1.9.0-3 (20 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
libssh21.10.0-31.10.0-3+deb12u1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
libssh21.11.1-1 ... 1.11.1-6 (7 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
libssh21.11.1-1, 1.11.1-2, 1.11.1-3, 1.11.1-41.11.1-5—

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 30× in last 7d / 138× 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 278 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-66032?
CVE-2026-66032 is a high vulnerability published on July 24, 2026. libssh2 through 1.11.1, fixed in commit 5e47761, contains a double-free vulnerability in the sftpopen() 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 SSHFXPOPEN with SSHFXPSTATUS…
When was CVE-2026-66032 disclosed?
CVE-2026-66032 was first published in the National Vulnerability Database on July 24, 2026, with the most recent update on August 7, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-66032 actively exploited?
CVE-2026-66032 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 62.1% of all scored CVEs.
What is the CVSS score of CVE-2026-66032?
CVE-2026-66032 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-66032?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-66032, 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-66032

Explore →

Is Your Infrastructure Affected by CVE-2026-66032?

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

Start Free Scan →Browse All CVEs