exploitarium

libssh2 through 1.11.1, fixed in commit 7acf3df 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. References https://nvd.nist.gov/vuln/detail/CVE-2026-55200 libssh2/libssh2#2052 libssh2/libssh2@97acf3d https://www.vulncheck.com/advisories/libssh2-out-of-bounds-write-via-unchecked-pac… https://github.com/bikini/exploitarium/tree/main/libssh2-cve-2026-55200-poc https://web.archive.org/web/20260623211210/https://github.com/bikini/exploitarium/…

I took a look at the Ghidra ones (because I use Ghidra), and I'm unimpressed: https://github.com/bikini/exploitarium/blob/main/ghidra-12.1... The first requires being able to overwrite binaries in the Swift tool directory. Yes, if you overwrite binaries executed by ghidra, you can trigger code execution. This is not a surprise. The second, idk, I'm not familiar with TraceRMI (but it's probably worth noting that "RMI" stands for Remote Method Invocation). The third is not a vulnerability in the slightest, they just demonstrate that native 7zip parsing code is reachable. Maybe there is a bug in the 7zip parser, but without that it's meaningless.