Free of Uninitialized Pointer in libssh2 Publickey List Cleanup
CVE-2026-58051 is a memory-safety vulnerability in libssh2 through version 1.11.1. When libssh2 expands its publickey list using SSH2_REALLOC, newly allocated entries are not zero-initialized before parser logic populates them. If parsing of a publickey subsystem response fails before initialization completes, execution can reach the cleanup path with one or more partially initialized or uninitialized entries still present. In that state, libssh2_publickey_list_free may operate on an uninitialized entry and free an uninitialized, attacker-influenceable attrs pointer. A malicious SSH server offering the publickey subsystem can trigger this condition by sending a malformed response to a connecting libssh2 client.
Are you exposed to this one?
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
Impact, mitigation & remediation
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Mitigation
If you can’t patch tonight, do this now.
Remediation
Patch, then assume compromise.
Exploits
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
Recent activity
7 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
The version that knows your environment.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.