CVE-2026-55200: libssh2 - Out-of-Bounds Write via Unchecked packet_length in transport.c

Published Jun 17, 2026
·
Updated

Last updated 30 June 2026

Other sources

libssh2 - Out-of-Bounds Write via Unchecked packetlength in transport.c

— Microsoft

libssh2 1.11.1, fixed in commit 97acf3d, contains an out-of-bounds write vulnerability in ssh2transportread() that fails to enforce upper bounds on packetlength field. Remote attackers can send crafted SSH packets with excessively large packetlength values to corrupt heap memory and achieve remote code execution.

— MITRE

libssh2 through 1.11.1, fixed in commit 7acf3df contains an out-of-bounds write vulnerability in ssh2transportread() that fails to enforce upper bounds on packetlength field. Remote attackers can send crafted SSH packets with excessively large packetlength values to corrupt heap memory and achieve remote code execution.

— Launchpad

Affected Software

13 affected componentsFixes available
libssh2 libssh2<=1.11.1
Microsoft azl3 libssh2 1.11.1-3<1.11.1-3
1.11.1-3
Microsoft azl3 libssh2 1.11.1-2<1.11.1-3
1.11.1-3
libssh2 libssh2=1.11.1
ubuntu/libssh2<1.11.1-1ubuntu0.25.10.2
1.11.1-1ubuntu0.25.10.2
ubuntu/libssh2<1.11.1-1ubuntu0.26.04.2
1.11.1-1ubuntu0.26.04.2
debian/libssh2
1.10.0-31.10.0-3+deb12u11.11.1-1+deb13u21.11.1-1+deb13u11.11.1-6
alpine/chromium-rust<1.96.1-r0
1.96.1-r0
alpine/libssh2<1.11.1-r2
1.11.1-r2
alpine/libssh2<1.11.1-r2
1.11.1-r2
alpine/libssh2<1.11.1-r3
1.11.1-r3
alpine/libssh2<1.11.1-r3
1.11.1-r3
alpine/rust<1.96.1-r0
1.96.1-r0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 1.11.1-3
  2. Upgrade

    Upgrade ubuntu/libssh2 to a version that resolves this vulnerability.

    Fixed in 1.11.1-1ubuntu0.25.10.2
  3. Upgrade

    Upgrade ubuntu/libssh2 to a version that resolves this vulnerability.

    Fixed in 1.11.1-1ubuntu0.26.04.2
  4. Upgrade

    Upgrade debian/libssh2 to a version that resolves this vulnerability.

    Fixed in 1.10.0-3Fixed in 1.10.0-3+deb12u1Fixed in 1.11.1-1+deb13u2Fixed in 1.11.1-1+deb13u1Fixed in 1.11.1-6
  5. Upgrade

    Upgrade alpine/chromium-rust to a version that resolves this vulnerability.

    Fixed in 1.96.1-r0
  6. Upgrade

    Upgrade alpine/libssh2 to a version that resolves this vulnerability.

    Fixed in 1.11.1-r2
  7. Upgrade

    Upgrade alpine/libssh2 to a version that resolves this vulnerability.

    Fixed in 1.11.1-r3
  8. Upgrade

    Upgrade alpine/rust to a version that resolves this vulnerability.

    Fixed in 1.96.1-r0

Event History

Jun 17, 2026
CVE Published
via MITRE·07:03 PM
Data Sourced
via MITRE·07:03 PM
DescriptionSeverityWeakness
Data Sourced
via OSV·08:17 PM
DescriptionSeverityAffected Software
Data Sourced
via NVD·08:17 PM
RemedyDescriptionSeverityWeaknessAffected Software
Jun 23, 2026
Exploit Published
via GitHub·09:13 PM
Jun 27, 2026
Data Sourced
via Microsoft·08:09 AM
DescriptionSeverityWeaknessAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Frequently Asked Questions

1

What is the severity of CVE-2026-55200?

The severity of CVE-2026-55200 is high, with a CVSS score of 8.1.

2

What does CVE-2026-55200 affect?

CVE-2026-55200 affects libssh2 versions up to 1.11.1.

3

How do I fix CVE-2026-55200?

To fix CVE-2026-55200, update libssh2 to the version that includes the fix from commit 7acf3df.

4

What type of attack is associated with CVE-2026-55200?

CVE-2026-55200 is associated with a remote code execution attack due to an out-of-bounds write.

5

What are the potential consequences of CVE-2026-55200?

The potential consequences of CVE-2026-55200 include heap memory corruption, which could lead to unauthorized access or control over the affected system.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203