Integer Overflow in libssh2 publickey subsystem attribute allocation
CVE-2026-58050 is a memory corruption vulnerability in libssh2 through 1.11.1 in the client-side handling of publickey-subsystem responses. libssh2 reads an attacker-controlled 32-bit attribute count from a server response and uses that value in the allocation expression num_attrs * sizeof(libssh2_publickey_attribute) without adequate bounds checking. On 32-bit platforms, this multiplication can overflow, resulting in an undersized heap allocation. A malicious SSH server can then cause the subsequent attribute-parsing loop to write beyond the allocated buffer, producing a heap buffer overflow in the 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
8 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.