CVE-2026-66033: libssh2 Integer Underflow DoS via AES-GCM Cipher Negotiation

Published Jul 24, 2026
·
Updated

Last updated 4 September 2026

Other sources

libssh2 Integer Underflow DoS via AES-GCM Cipher Negotiation

Microsoft

libssh2 through 1.11.1, fixed in commit a2ed82d, contains a pre-authentication integer underflow vulnerability in the ssh2ciphercrypt() function in src/openssl.c that allows a malicious SSH server to crash any connecting client by negotiating AES-GCM ciphers during handshake. Attackers can exploit the underflow in the expression computing blocksize minus aadlen minus authentication tag length to trigger an out-of-bounds read and a memcpy call with a near-SIZEMAX length argument, causing immediate process crash before any authentication occurs.

MITRE

Affected Software

4 affected componentsFixes available
libssh2 libssh2<=1.11.1
libssh2 libssh2<=1.11.1
Microsoft azl3 libssh2 1.11.1-4<1.11.1-5
1.11.1-5
debian/libssh2<=1.11.1-1+deb13u1
1.10.0-31.11.1-6

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-5
  2. Upgrade

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

    Fixed in 1.10.0-3Fixed in 1.11.1-6
  3. Upgrade

    Upgrade libssh2 to a version that resolves this vulnerability.

    Fixed in 1.11.1Patch a2ed82d
  4. Compensating control

    Mitigate pre-authentication crash risk by limiting or filtering inbound SSH connections (e.g., via firewall/ACL) to reduce exposure to malicious servers performing AES-GCM cipher negotiation.

Event History

Jul 24, 2026
CVE Published
via MITRE·04:35 PM
Data Sourced
via MITRE·04:35 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·05:17 PM
RemedyDescriptionSeverityWeaknessAffected Software
Jul 26, 2026
Data Sourced
via Microsoft·08:04 AM
DescriptionSeverityWeaknessAffected Software
Updated
via Microsoft·08:04 AM
DescriptionSeverity
Sep 3, 2026
Data Sourced
via Launchpad·02:54 PM
Description
Data Sourced
via Debian·02:54 PM
DescriptionAffected Software
Sep 4, 2026
Data Sourced
via Ubuntu·02:54 PM
RemedyDescriptionSeverityAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-66033?

CVE-2026-66033 has a severity rating of high with a score of 7.5.

2

What type of vulnerability is CVE-2026-66033?

CVE-2026-66033 is classified as an integer underflow vulnerability.

3

How can CVE-2026-66033 be exploited?

CVE-2026-66033 can be exploited by a malicious SSH server to crash a client by negotiating AES-GCM ciphers during the handshake.

4

How do I fix CVE-2026-66033?

To fix CVE-2026-66033, upgrade to libssh2 version 1.11.2 or later, where the vulnerability has been addressed.

5

What software is affected by CVE-2026-66033?

CVE-2026-66033 affects libssh2 versions up to and including 1.11.1.

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