cve.bz

CVE-2026-55200 libssh2 libssh2: Integer Overflow to Buffer Overflow

9.2 criticalExploit referenceEPSS 3.9%Fix available

Critical (9.2) in libssh2 libssh2. EPSS 3.9% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 4.0

9.2 critical
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

CVSS 3.1

8.3 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:L
EPSS
3.9% (unchanged from 3.9% a week ago; 4.0% 30 days ago) estimated probability of exploitation activity in the next 30 days; 90th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: total, assessed 2026-06-17. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-680 Integer Overflow to Buffer Overflow
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-55200 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-55200?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-55200?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-55200 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
libssh2:libssh21.11.1

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian13libssh21.11.1-1+deb13u1DEBIAN-CVE-2026-55200
Debian14libssh21.11.1-4DEBIAN-CVE-2026-55200
Ubuntu25.10libssh21.11.1-1ubuntu0.25.10.2UBUNTU-CVE-2026-55200
Ubuntu26.04:LTSlibssh21.11.1-1ubuntu0.26.04.2UBUNTU-CVE-2026-55200
Red Hathummingbird:1libssh2, libssh2-docs, libssh2-devel0:1.11.1-8.hum1RHSA-2026:29950
SUSELinux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0libssh2_org1.11.1-160000.4.1SUSE-SU-2026:22364-1
SUSELinux Micro 6.2libssh2_org1.11.1-160000.4.1SUSE-SU-2026:22284-1
openSUSELeap 16.0libssh2_org1.11.1-160000.4.1openSUSE-SU-2026:21057-1
openSUSETumbleweedlibssh2_org1.11.1-3.1openSUSE-SU-2026:11109-1
Alpinev3.21, v3.22libssh21.11.1-r2ALPINE-CVE-2026-55200
Alpinev3.23, v3.24libssh21.11.1-r3ALPINE-CVE-2026-55200
Alpinev3.24rust, chromium-rust1.96.1-r0ALPINE-CVE-2026-55200
Azure Linux3libssh21.11.1-3AZL-90927
Azure Linux3rustno fix listedAZL-108519
Alpaquita23, streamlibssh21.11.1-r3BELL-CVE-2026-55200
Alpaquita25libssh21.11.1-r2BELL-CVE-2026-55200
Alpaquitastreamrust1.96.1-r0BELL-CVE-2026-55200

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Red Hat Security Data © Red Hat, Inc., CC BY 4.0; SUSE security data, CC BY 4.0; the Alpine secdb, CC BY-SA 4.0; Microsoft's Azure Linux vulnerability data, MIT; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Red Hat · SUSE · openSUSE · Alpine · Alpaquita.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

An Important out-of-bounds write vulnerability was discovered in libssh2. As it only impacts client installations of the library, exploitation would require a victim to initiate an SSH connection to an attacker-controlled server. This means an attacker must first redirect client connections via DNS poisoning, a man-in-the-middle, or compromise of a trusted host. While the vulnerability does not require authentication and requires no special configuration, the client redirection prerequisites significantly limit the practical attack surface compared to a server-side flaw.

The integer overflow provides uncontrolled access to the heap, which reliably crashes the client process but is unlikely to achieve remote code execution in practice. Weaponizing the overflow for code execution would require a separate information disclosure vulnerability to defeat ASLR, along with a specific heap layout to place exploitable structures adjacent to the undersized allocation. On RHEL, ASLR is enabled by default and glibc's heap metadata integrity checks further raise the bar, making denial of service the realistic impact for most deployments.

RHEL 8.1 and later do not include libssh2 as a supported product component. Hence, they are not affected by this flaw.

Red Hat's mitigation

The primary mitigation is strict network access control. Ensure libssh2 clients only connect to trusted SSH servers, and use firewalls to block untrusted incoming connections if libssh2 is deployed as a server-side application.

ProductPackageStateAdvisory
Red Hat Hardened Imageslibssh2-main-1.11.1-8.hum1Fixed 2026-06-25RHSA-2026:29950
Red Hat Enterprise Linux 6libssh2Out of support scope
Red Hat Enterprise Linux 7libssh2Not affected
Red Hat Enterprise Linux 8virt:rhel/libssh2Out of support scope

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-55200.

GitHub PoC

Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-680 (11).

References

Check your stackJSON