Linux · SUSE Linux Enterprise · Security advisory · August 10, 2026
SUSE-SU-2026:3541-1: libssh2_org security update
SUSE-SU-2026:3541-1, released August 10, 2026, fixes 8 CVEs in libssh2_org (version 1.11.0-150600.20.6.1). None of them is reported as exploited. Patch Radar priority: High.
High
CVEs closed
8
None rated Critical
Exploited
0
None reported
Highest CVSS
8.8
Base score, 0 to 10
Highest EPSS
0.0065
51st percentile
Priority of the 8 CVEs
Patch now 0
Urgent 0
High 6
Routine 2
Fixed package versions
| Product | Release | Fixed in |
|---|---|---|
| libssh2_org | sles 15.6 | 1.11.0-150600.20.6.1 |
| libssh2_org | sles 15.7 | 1.11.0-150600.20.6.1 |
CVEs this fix closes
| Priority | CVE | Title | CVSS | EPSS | Exploitation |
|---|---|---|---|---|---|
| High | CVE-2026-66033 | libssh2 Integer Underflow DoS via AES-GCM Cipher Negotiation | 7.5 | 0.0058 | None reported |
| High | CVE-2026-66035 | libssh2 Heap Buffer Overflow via ETM Cipher Negotiation | 7.5 | 0.0047 | None reported |
| High | CVE-2026-7598 | libssh2 userauth.c userauth_password integer overflow | 7.3 | 0.0047 | None reported |
| High | CVE-2026-66032 | libssh2 Double-Free Heap Corruption via sftp_open() | 8.8 | 0.0045 | None reported |
| High | CVE-2026-58050 | libssh2 - Integer Overflow in publickey Subsystem Attribute Allocation | 7.5 | 0.0044 | None reported |
| High | CVE-2026-66034 | libssh2 Heap Out-of-Bounds Read via publickey subsystem | 7.5 | 0.0040 | None reported |
| Routine | CVE-2025-15661 | libssh2 - Heap Buffer Over-read via sftp_symlink() in sftp.c | 6.5 | 0.0065 | None reported |
| Routine | CVE-2026-58051 | libssh2: libssh2 through 1.11.1 grows its publickey list with SSH2_REALLOC but does not zero-initialize new entries before par... | n/a | 0.0028 | None reported |
Showing 1 to 8 of 8
1
Patch Radar data is free to use with attribution. Terms and how to credit it.
Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.