Security Advisory

CVE-2026-55200: libssh2 Packet-Length Overflow

Last updated:
  • CVE-2026-55200

CVE-2026-55200 is a heap out-of-bounds write in libssh2 1.11.1: ssh2_transport_read() does not cap the packet_length field, so a malicious SSH server can corrupt memory in the connecting client. NVD scores it 8.3. No libssh2 release has the fix; it exists as commit 97acf3d, and OpenWrt still builds 1.11.1 unpatched.

Vulnerability summary

CVSS base score

8.3

High severity

EPSS score (FIRST)

3.9%

Probability of exploitation in the wild in the next 30 days

CISA KEV catalog

No

Not listed

Published

Vulnerability ID: CVE-2026-55200 · Source: NVD

Affected components

ComponentCPEVersion range
libssh2cpe:2.3:a:libssh2:libssh2:1.11.1:*:*:*:*:*:*:*1.11.1 (fixed by upstream commit 97acf3d; no release contains the fix as of 2026-11-16)
OpenWrt packages feed: libssh2cpe:/a:libssh2:libssh21.11.1 with no patches on the master and openwrt-25.12 branches (read 2026-11-16)

What does this mean for affected devices?

CVE-2026-55200 is an integer-overflow-to-buffer-overflow flaw (CWE-680), which results in an out-of-bounds heap write (the CWE-787 class), in libssh2's transport layer. NVD's record says libssh2 1.11.1 "fails to enforce upper bounds on packet_length field" and that remote attackers "can send crafted SSH packets with excessively large packet_length values to corrupt heap memory and achieve remote code execution". NVD scores it 8.3 with vector CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:L; VulnCheck, the CNA, gives 8.1 under CVSS 3.1 (NVD).

The fix is commit 97acf3d, "transport.c: Additional boundary checks for packet length", dated 2026-06-12. On 2026-11-16 the libssh2 home page still lists 1.11.1, released on 2024-10-16, as the download, so no release carries the fix and a scanner that treats "latest version" as clean will miss it. libssh2 is client-only, so the attacker is the SSH server the device connects to, or anyone who can impersonate it.

Firmware build systems differ. OpenWrt's libssh2 package for openwrt-25.12, like the master branch, builds plain 1.11.1 with no patch directory, so an OpenWrt-based image that enables libssh2, for example for libcurl SFTP uploads, carries the flaw unless the product adds the patch. Buildroot's libssh2.mk applies the fix as patch 0003 and marks the CVE as ignored, and the OpenEmbedded-Core recipe carries CVE-2026-55200.patch. Our libssh and libssh2 vulnerabilities in embedded firmware guide walks through triaging exactly this case in a gateway image.

The CVE is not in the CISA KEV catalog as of 2026-11-16 (catalog version 2026.11.13); FIRST EPSS gives it 0.039, the 90th percentile, in the 2026-11-15 dataset (CISA KEV, FIRST EPSS). The Debian tracker shows trixie fixed in 1.11.1-1+deb13u1 (DSA-6365-1), and bullseye and bookworm not affected because the vulnerable code is not present in their older versions.

Device makers on 1.11.1 should apply commit 97acf3d, using the Buildroot or OpenEmbedded-Core patches as a reference, then pin server host keys and limit which servers the device contacts. Our memory corruption fix guide and firmware diffing guide cover proving the backport reached the shipped library.

How to fix this class of issueThis advisory's weakness class is Memory corruption. Our practical guide covers how to detect, fix, verify and disclose it: How to fix memory corruption in embedded firmware.

Evidence

  • libssh2 1.11.1 fails to enforce upper bounds on packet_length in ssh2_transport_read(); NVD Primary CVSS v3.1 8.3; VulnCheck 8.1; CWE-680. — NVD
  • Fix commit 97acf3d, transport.c: Additional boundary checks for packet length (#2052), dated 2026-06-12. — libssh2 commit 97acf3d
  • libssh2 1.11.1, released on 2024-10-16, is the current download on 2026-11-16. — libssh2 home page
  • openwrt-25.12 libssh2 package: PKG_VERSION 1.11.1, Makefile only, no patches. — OpenWrt packages (openwrt-25.12)
  • Buildroot applies patch 0003 and sets LIBSSH2_IGNORE_CVES += CVE-2026-55200. — Buildroot libssh2.mk
  • OpenEmbedded-Core libssh2 1.11.1 recipe includes CVE-2026-55200.patch. — OpenEmbedded-Core libssh2 recipe
  • Not in the CISA KEV catalog as of 2026-11-16 (catalog version 2026.11.13). — CISA KEV
  • EPSS 0.03877 (90th percentile), dataset 2026-11-15, read 2026-11-16. — FIRST EPSS

Related advisories

Sources

  1. NVD
  2. libssh2 commit 97acf3d
  3. libssh2 home page
  4. OpenWrt packages: libssh2 Makefile (openwrt-25.12)
  5. Buildroot: libssh2.mk
  6. OpenEmbedded-Core: libssh2 1.11.1 recipe
  7. Debian Security Tracker
  8. CISA KEV
  9. FIRST EPSS

Frequently asked questions

Is there a libssh2 release that fixes CVE-2026-55200?

No. On 2026-11-16 the libssh2 home page still lists 1.11.1 (2024-10-16) as the current release, and the fix exists only as commit 97acf3d, so products must apply the patch (per libssh2 and NVD).

Who can exploit CVE-2026-55200 against a device?

The SSH server the device connects to. NVD describes crafted packets with excessively large packet_length values, and libssh2 is a client library, so a malicious, compromised or impersonated server is the attacker (per NVD).

Do OpenWrt, Buildroot and Yocto ship the fix?

On 2026-11-16 OpenWrt builds plain 1.11.1 with no patches, while Buildroot applies the fix as a patch and OpenEmbedded-Core carries CVE-2026-55200.patch (per the OpenWrt, Buildroot and OpenEmbedded-Core package files).

Is CVE-2026-55200 in the CISA KEV catalog?

No, not as of 2026-11-16 (catalog version 2026.11.13). FIRST EPSS gives it 0.039, the 90th percentile, in the 2026-11-15 dataset (per CISA KEV and FIRST EPSS).