libssh2 through 1.11.1 grows its publickey list with SSH2_REALLOC but does not zero-initialize new entries before parsing populates them, so a parse failure reaching the cleanup path leaves libssh2_publickey_list_free operating on an uninitialized entry. A malicious SSH server offering the publickey subsystem can use a malformed response to make cleanup free an uninitialized, attacker-influenceable attrs pointer in a connecting libssh2 client.
References
Configurations
History
30 Jun 2026, 17:42
| Type | Values Removed | Values Added |
|---|---|---|
| CPE | cpe:2.3:a:libssh2:libssh2:*:*:*:*:*:*:*:* | |
| First Time |
Libssh2 libssh2
Libssh2 |
|
| References | () https://github.com/bikini/exploitarium/tree/main/libssh2-publickey-list-calc-poc - Broken Link | |
| References | () https://github.com/libssh2/libssh2/blob/master/src/publickey.c - Product | |
| References | () https://www.vulncheck.com/advisories/libssh2-free-of-uninitialized-pointer-in-publickey-list-cleanup - Third Party Advisory |
28 Jun 2026, 02:16
| Type | Values Removed | Values Added |
|---|---|---|
| New CVE |
Information
Published : 2026-06-28 02:16
Updated : 2026-06-30 17:42
NVD link : CVE-2026-58051
Mitre link : CVE-2026-58051
CVE.ORG link : CVE-2026-58051
JSON object : View
Products Affected
libssh2
- libssh2
CWE
CWE-908
Use of Uninitialized Resource
