libssh2 1.11.1, fixed in commit 97acf3d, contains an out-of-bounds write vulnerability in ssh2_transport_read() that fails to enforce upper bounds on packet_length field. Remote attackers can send crafted SSH packets with excessively large packet_length values to corrupt heap memory and achieve remote code execution.
Fix
Public exploits 3
- 0xBlackash/CVE-2026-55200 PoC on GitHub
- kaleth4/CVE-2026-55200 PoC on GitHub
- xd20111/CVE-2026-55200 PoC on GitHub
Each line links to the index that lists it, never to exploit code. Exploit-DB's "verified" and a Metasploit rank of good or better count as verified; a PoC-in-GitHub entry is a repository's claim.
Patch, vendor advisory and mitigation references on NVD 2
- https://github.com/libssh2/libssh2/commit/97acf3dfda80c91c3a8c9f2372546301d4a1a7a8 Patch
- https://github.com/libssh2/libssh2/pull/2052 Patch
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 9.2 · libssh2NVD modified 2026-10-22 19:17
Affected (CPE criteria) 1
cpe:2.3:a:libssh2:libssh2:1.11.1:*:*:*:*:*:*:*
References 4
- https://github.com/libssh2/libssh2/commit/97acf3dfda80c91c3a8c9f2372546301d4a1a7a8 Patch
- https://github.com/libssh2/libssh2/pull/2052 Patch
- https://www.vulncheck.com/advisories/libssh2-out-of-bounds-write-via-unchecked-packet-length-in-transport-c Third Party Advisory
- https://web.archive.org/web/20260623211210/https://github.com/bikini/exploitarium/tree/main/libssh2-cve-2026-55200-poc Exploit, Third Party Advisory