Debian published four advisories in 2026 for two SSH libraries: libssh (DSA-6410-1 for Debian 13 on 2 August, DLA-4844-1 for Debian 12 on 20 October) and libssh2 (DSA-6365-1 for Debian 13 on 25 June, DLA-4773-1 for Debian 12 on 5 September). Neither library is OpenSSH: your sshd server and the ssh command come from openssh-server and openssh-client, which do not depend on them. The risk sits in programs that embed these libraries to make SSH or SFTP connections, mostly as clients talking to a server that could be malicious.
At a glance
| Library | Debian 13 (trixie) | Debian 12 (bookworm) | Binary packages |
|---|---|---|---|
| libssh | 0.11.5-0+deb13u1 (DSA-6410-1, 15 CVEs in the announcement) | 0.10.6-0+deb12u3 (DLA-4844-1, 13 CVEs) | libssh-4; bookworm also libssh-gcrypt-4 |
| libssh2 | 1.11.1-1+deb13u1 (DSA-6365-1, 4 CVEs), then 1.11.1-1+deb13u2 in the regular trixie archive | 1.10.0-3+deb12u1 (DLA-4773-1, 6 CVEs) | libssh2-1t64 (trixie), libssh2-1 (bookworm) |
Severity: High overall, based on the CNA scores for libssh2 (CVSS 3.1 of 8.8 for CVE-2026-66032 and 8.1 for CVE-2026-55200). libssh's own advisories score its issues at most 6.7. None of these CVEs is in the CISA Known Exploited Vulnerabilities catalog as of 30 October 2026.
What the vulnerabilities are
libssh
Debian describes the libssh issues as possibly leading to "denial of service, information disclosure and potentially the execution of arbitrary code". The main ones, from the libssh advisories and DLA-4844-1:
- CVE-2026-15370 (trixie only): a possible stack buffer overflow in libssh's SFTP server when listing a directory with very long file names that an attacker controls, which libssh says could lead to code execution. It affects libssh 0.11.0 and later, so bookworm's 0.10.6 is not affected.
- CVE-2026-0964: a malicious SCP server can send a path that escapes the working directory.
- CVE-2026-59847: with the OpenSSL backend, a failed AES-GCM tag check could be treated as success, allowing silent modification of data.
- CVE-2026-59850: data arriving on a remotely closed channel could reach a callback after the channel was freed.
- Several denial-of-service and parsing bugs, such as CVE-2026-0966, CVE-2026-59843 and CVE-2026-59844. CVE-2026-59849 (an infinite loop with certificate authentication) affects trixie only.
libssh2
libssh2 is a client-side library, so these flaws are triggered by a malicious server or a man in the middle. Debian says they "could result in memory disclosure, denial of service or potentially the execution of arbitrary code".
- CVE-2026-55200 (trixie only): an out-of-bounds heap write when reading SSH packets with a huge length field. The Debian tracker marks bookworm as not affected.
- CVE-2026-66032: a double free in
sftp_open()reachable from a malicious server during SFTP setup. - CVE-2026-66034, CVE-2026-58050, CVE-2026-58051: memory errors in the publickey subsystem.
- CVE-2025-15661, CVE-2026-7598, CVE-2026-55199: a heap over-read in SFTP symlink handling, an integer overflow in password authentication, and a CPU loop from a crafted extension count (the last is trixie only).
DSA-6365-1 fixed the first group for trixie in June. The four publickey and SFTP fixes from DLA-4773-1 reached trixie later as 1.11.1-1+deb13u2 in the regular stable archive rather than through a DSA, so make sure your trixie sources include the main trixie suite as well as trixie-security.
Are you affected?
On Debian 13, libcurl4t64 and libcurl3t64-gnutls (and therefore curl, PHP's curl extension and git over HTTPS) depend on libssh2-1t64; on Debian 12, libcurl4 depends on libssh2-1. PHP's ssh2 extension also uses libssh2, and QEMU's qemu-block-extra uses libssh. Check what you have:
dpkg -l 'libssh-*' 'libssh2-*'
apt policy libssh-4 libssh2-1t64 # Debian 13
apt policy libssh-4 libssh2-1 # Debian 12Compare with the versions in the table. Debian 11 (bullseye) is past the end of LTS (31 August 2026) and should be upgraded.
How to update
sudo apt update
sudo apt upgradeUbuntu packages differ; check Ubuntu Security Notices.
Restart or reboot?
No reboot is needed. Programs that loaded the old library keep it until restarted. One-off commands such as curl or git pick up the fix on their next run; long-running services, for example PHP-FPM with the ssh2 or curl extension, need a restart:
sudo needrestart -r l
sudo systemctl restart php8.4-fpm
Sources
- security-tracker.debian.org/tracker/DSA-6410-1
- debian.org/security/2026/dsa-6410
- lists.debian.org/debian-security-announce/2026/msg00321.html
- security-tracker.debian.org/tracker/DLA-4844-1
- lists.debian.org/debian-lts-announce/2026/10/msg00038.html
- security-tracker.debian.org/tracker/DSA-6365-1
- debian.org/security/2026/dsa-6365
- lists.debian.org/debian-security-announce/2026/msg00276.html
- security-tracker.debian.org/tracker/DLA-4773-1
- lists.debian.org/debian-lts-announce/2026/09/msg00008.html
- libssh.org/security/advisories
- libssh.org/security/advisories/CVE-2026-15370.txt
- libssh.org/security/advisories/CVE-2026-59847.txt
- security-tracker.debian.org/tracker/CVE-2026-15370
- security-tracker.debian.org/tracker/CVE-2026-55200
- security-tracker.debian.org/tracker/CVE-2026-66032
- cve.org/CVERecord?id=CVE-2026-66032
- cve.org/CVERecord?id=CVE-2026-55200
- packages.debian.org/trixie/libssh2-1t64
- packages.debian.org/trixie/libcurl4t64
- packages.debian.org/bookworm/libcurl4
- packages.debian.org/trixie/php8.4-ssh2
- packages.debian.org/trixie/qemu-block-extra
- packages.debian.org/trixie/openssh-server
- manpages.debian.org/trixie/needrestart/needrestart.1.en.html
- security-tracker.debian.org/tracker/libssh2
Comments
0 total · 0 threads