CVE-2026-55200: libssh2 - Out-of-Bounds Write via Unchecked packet_length in transport.c
Noroxi assessment
Priority: Monitor (action score 37/100)
- Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 3.8% (FIRST EPSS); higher than 90.2% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: libssh2 libssh2 97acf3dfda80c91c3a8c9f2372546301d4a1a7a8; azl3 libssh2 1.11.1-2 on Azure Linux 3.0 1.11.1-3; azl3 libssh2 1.11.1-3 on Azure Linux 3.0 1.11.1-3.
Low priority for now. Upgrade to libssh2 libssh2 97acf3dfda80c91c3a8c9f2372546301d4a1a7a8; azl3 libssh2 1.11.1-2 on Azure Linux 3.0 1.11.1-3; azl3 libssh2 1.11.1-3 on Azure Linux 3.0 1.11.1-3 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Jun 17, 2026
- Updated
- Oct 22, 2026
- EPSS
- 3.8% · 90th percentile
- CWE
- CWE-680
Report tools
Action score
37
Monitor
Low priority for now.
- CVSS
- 36 / 40 · 9.2 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 3.8%
CISA SSVC decision
- Exploitation
- proof of concept
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · VulnCheck
- 9.2
- NVD has not scored this yet; the score shown is the CNA’s.
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
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- Proof of concept exists, no weaponized module
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| libssh2 | libssh2 | cpe:2.3:a:libssh2:libssh2 |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- libssh2 libssh21.11.1
Versions reported by the vendor
Affected version ranges reported by the assigning authority (VulnCheck). Independent of NVD's CPE analysis and usually ahead of it.
libssh2 libssh2
- 1.11.1affected
- 1c3f1b7da588f2652260285529ec3c1f1125eb4e and later · before 97acf3dfda80c91c3a8c9f2372546301d4a1a7a8affected · git
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.21 | libssh2 | before 1.11.1-r2 | 1.11.1-r2 |
| Alpine:v3.23 | libssh2 | before 1.11.1-r3 | 1.11.1-r3 |
| Alpine:v3.24 | chromium-rust | before 1.96.1-r0 | 1.96.1-r0 |
| Alpine:v3.24 | rust | before 1.96.1-r0 | 1.96.1-r0 |
| Debian:13 | libssh2 | before 1.11.1-1+deb13u1 | 1.11.1-1+deb13u1 |
| Debian:14 | libssh2 | before 1.11.1-4 | 1.11.1-4 |
| openSUSE:Leap 16.0 | libssh2_org | before 1.11.1-160000.4.1 | 1.11.1-160000.4.1 |
| openSUSE:Tumbleweed | libssh2_org | before 1.11.1-3.1 | 1.11.1-3.1 |
| Red Hat:hummingbird:1 | libssh2 | before 0:1.11.1-8.hum1 | 0:1.11.1-8.hum1 |
| Red Hat:hummingbird:1 | libssh2-devel | before 0:1.11.1-8.hum1 | 0:1.11.1-8.hum1 |
| Red Hat:hummingbird:1 | libssh2-docs | before 0:1.11.1-8.hum1 | 0:1.11.1-8.hum1 |
| SUSE:Linux Micro 6.2 | libssh2_org | before 1.11.1-160000.4.1 | 1.11.1-160000.4.1 |
Same product
libssh2: all recordsOther highest-scoring records for the same primary product.
- CVE-2019-3861An out of bounds read flaw was discovered in libssh2 before 1.8.1 in the way SSH packets with a padding length value greater than the packet38Monitor
- CVE-2019-3860An out of bounds read flaw was discovered in libssh2 before 1.8.1 in the way SFTP packets with empty payloads are parsed.38Monitor
- CVE-2019-3858An out of bounds read flaw was discovered in libssh2 before 1.8.1 when a specially crafted SFTP packet is received from the server.38Monitor
Published before and after this one in the same product
- ← EarlierCVE-2026-7598May 1, 2026 · libssh2 userauth.c userauth_password integer overflow27Monitor
- ← EarlierCVE-2026-55199Jun 17, 2026 · libssh2 - Pre-Authentication DoS via SSH_MSG_EXT_INFO Handler32Monitor
- Later →CVE-2025-15661Jun 18, 2026 · libssh2 - Heap Buffer Over-read via sftp_symlink() in sftp.c33Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| libssh2 libssh2 | 97acf3dfda80c91c3a8c9f2372546301d4a1a7a8 | Vendor (CNA) |
| azl3 libssh2 1.11.1-2 on Azure Linux 3.0 | 1.11.1-3 · CBL-Mariner Releases | Microsoft (MSRC) |
| azl3 libssh2 1.11.1-3 on Azure Linux 3.0 | 1.11.1-3 · CBL-Mariner Releases | Microsoft (MSRC) |
| alpine:chromium-rust | 1.96.1-r0 · Alpine:v3.24 | Package registry (OSV) |
| alpine:libssh2 | 1.11.1-r2 · Alpine:v3.21 | Package registry (OSV) |
| alpine:rust | 1.96.1-r0 · Alpine:v3.24 | Package registry (OSV) |
| debian:libssh2 | 1.11.1-1+deb13u1 · Debian:13 | Package registry (OSV) |
| opensuse:libssh2_org | 1.11.1-3.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| red hat:libssh2 | 0:1.11.1-8.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:libssh2-devel | 0:1.11.1-8.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:libssh2-docs | 0:1.11.1-8.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| suse:libssh2_org | 1.11.1-160000.4.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
Exploit status
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Proof-of-concept repository on GitHub ×3
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Proof-of-concept repository on GitHub | stars:10 | 2026-06-23 |
| Proof-of-concept repository on GitHub | stars:4 | 2026-06-29 |
| Proof-of-concept repository on GitHub | stars:0 | 2026-07-02 |
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- First PoC+5 d
- TodayNov 7, 2026+143 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- X
Weakness class (CWE)
CWE-680 · Integer Overflow to Buffer OverflowCVSS vector
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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Buffer Overflow via Environment VariablesCAPEC-10likelihood: High · High
- Overflow BuffersCAPEC-100likelihood: High · Very High
- Client-side Injection-induced Buffer OverflowCAPEC-14likelihood: Medium · High
- Filter Failure through Buffer OverflowCAPEC-24likelihood: High · High
- Buffer Overflow via Symbolic LinksCAPEC-45likelihood: High · High
- Overflow Variables and TagsCAPEC-46likelihood: High · High
- Buffer Overflow via Parameter ExpansionCAPEC-47likelihood: Medium · High
- String Format Overflow in syslog()CAPEC-67likelihood: High · Very High
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.