Client heap corruption via SFTP response double free
Published Jul 24, 2026 · Updated Jul 24, 2026
Double free in libssh2 through 1.11.1 allows remote attackers controlling an SSH server to corrupt a client heap during SFTP open. In sftp_open() in src/sftp.c, an FX_OK status frees the response buffer without clearing its pointer, so a later sftp_packet_require() error frees it again. The client must authenticate to an attacker-controlled server and open an SFTP session; heap corruption can overlap allocations and overwrite function pointers on glibc systems.
Summary
What happened
Double free in libssh2 through 1.11.1 allows remote attackers controlling an SSH server to corrupt a client heap during SFTP open. In sftp_open() in src/sftp.c, an FX_OK status frees the response buffer without clearing its pointer, so a later sftp_packet_require() error frees it again. The client must authenticate to an attacker-controlled server and open an SFTP session; heap corruption can overlap allocations and overwrite function pointers on glibc systems.
The record
- CVE
- CVE-2026-66032
- Published
- Jul 24, 2026
- Updated
- Jul 24, 2026
- Vendor
- libssh2
- Product
- libssh2
- Classifications
- CWE-415, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 24, 2026CVE publishedPublication date reported by the CVE source.
- Jul 24, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=1.11.1
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo