CVSS 4.0
9.2 criticalCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:NCritical (9.2) in libssh2 libssh2. EPSS 3.9% estimated probability of exploitation activity in the next 30 days.
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:NCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:LExplain 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.
From the NVD's CPE matches.
| Product | Affected |
|---|---|
| libssh2:libssh2 | 1.11.1 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 13 | libssh2 | 1.11.1-1+deb13u1 | DEBIAN-CVE-2026-55200 |
| Debian | 14 | libssh2 | 1.11.1-4 | DEBIAN-CVE-2026-55200 |
| Ubuntu | 25.10 | libssh2 | 1.11.1-1ubuntu0.25.10.2 | UBUNTU-CVE-2026-55200 |
| Ubuntu | 26.04:LTS | libssh2 | 1.11.1-1ubuntu0.26.04.2 | UBUNTU-CVE-2026-55200 |
| Red Hat | hummingbird:1 | libssh2, libssh2-docs, libssh2-devel | 0:1.11.1-8.hum1 | RHSA-2026:29950 |
| SUSE | Linux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0 | libssh2_org | 1.11.1-160000.4.1 | SUSE-SU-2026:22364-1 |
| SUSE | Linux Micro 6.2 | libssh2_org | 1.11.1-160000.4.1 | SUSE-SU-2026:22284-1 |
| openSUSE | Leap 16.0 | libssh2_org | 1.11.1-160000.4.1 | openSUSE-SU-2026:21057-1 |
| openSUSE | Tumbleweed | libssh2_org | 1.11.1-3.1 | openSUSE-SU-2026:11109-1 |
| Alpine | v3.21, v3.22 | libssh2 | 1.11.1-r2 | ALPINE-CVE-2026-55200 |
| Alpine | v3.23, v3.24 | libssh2 | 1.11.1-r3 | ALPINE-CVE-2026-55200 |
| Alpine | v3.24 | rust, chromium-rust | 1.96.1-r0 | ALPINE-CVE-2026-55200 |
| Azure Linux | 3 | libssh2 | 1.11.1-3 | AZL-90927 |
| Azure Linux | 3 | rust | no fix listed | AZL-108519 |
| Alpaquita | 23, stream | libssh2 | 1.11.1-r3 | BELL-CVE-2026-55200 |
| Alpaquita | 25 | libssh2 | 1.11.1-r2 | BELL-CVE-2026-55200 |
| Alpaquita | stream | rust | 1.96.1-r0 | BELL-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 rates this Moderate.
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.
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.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Hardened Images | libssh2-main-1.11.1-8.hum1 | Fixed 2026-06-25 | RHSA-2026:29950 |
| Red Hat Enterprise Linux 6 | libssh2 | Out of support scope | |
| Red Hat Enterprise Linux 7 | libssh2 | Not affected | |
| Red Hat Enterprise Linux 8 | virt:rhel/libssh2 | Out 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.
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.
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).