CVE-2026-58051 is a memory-safety vulnerability in libssh2 through version 1.11.1 affecting client-side handling of the SSH publickey subsystem. When libssh2 expands its internal publickey list using reallocation, newly added entries are not zero-initialized before parser population occurs. If parsing of a server-supplied publickey response fails before the new entry is fully initialized, execution can reach the cleanup path with partially or wholly uninitialized list elements still present. During cleanup, libssh2_publickey_list_free may operate on such an uninitialized entry and attempt to free an uninitialized, attacker-influenceable attrs pointer. A malicious SSH server that offers the publickey subsystem can trigger this condition by returning a malformed response to a connecting libssh2 client.
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.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
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.
13 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A use-after-free vulnerability in libssh2 during publickey list cleanup caused by freeing an uninitialized pointer.
A memory corruption vulnerability in libssh2 through 1.11.1 caused by failure to zero-initialize newly reallocated publickey list entries, allowing a malicious SSH server to trigger cleanup on an uninitialized attacker-influenceable pointer in a connecting client.
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.