Code execution via unchecked SSH packet length
Published Jun 17, 2026 · Updated Jul 14, 2026
Heap corruption in libssh2 1.11.1 and earlier allows remote attackers to execute code via crafted SSH transport packets. In src/transport.c, ssh2_transport_read() accepts an oversized packet_length before adding framing and authentication lengths, allowing integer wraparound to underallocate the heap buffer. The affected path requires an encrypted SSH session using a cipher that requires full-packet processing; execution occurs in the consuming client application's context.
Summary
What happened
Heap corruption in libssh2 1.11.1 and earlier allows remote attackers to execute code via crafted SSH transport packets. In src/transport.c, ssh2_transport_read() accepts an oversized packet_length before adding framing and authentication lengths, allowing integer wraparound to underallocate the heap buffer. The affected path requires an encrypted SSH session using a cipher that requires full-packet processing; execution occurs in the consuming client application's context.
The record
- CVE
- CVE-2026-55200
- Published
- Jun 17, 2026
- Updated
- Jul 14, 2026
- Vendor
- The libssh2 Project
- Product
- libssh2
- Classifications
- CWE-680, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 17, 2026CVE publishedPublication date reported by the CVE source.
- Jul 14, 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?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
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
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started