CVE-2026-66032 is a double-free vulnerability affecting libssh2 versions through 1.11.1. The flaw occurs in the SFTP open-request handling path when a malicious SSH server replies to an SSH_FXP_OPEN request with an SSH_FXP_STATUS response indicating FX_OK. libssh2 releases the response buffer during this handling, then can release the same pointer again if a subsequent packet-requirement operation fails, including with LIBSSH2_ERROR_CHANNEL_PACKET_EXCEEDED. This corrupts the heap of the client application.
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.
11 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A double-free flaw in libssh2 sftp_open() during SFTP session setup. A malicious server can trigger it through a crafted SSH_FXP_OPEN response sequence.
A double-free flaw in a libssh2 SFTP session that can enable arbitrary code execution.
A specific vulnerability tracked as CVE-2026-66032 referenced in a Unity Linux local security check advisory.
A high-severity double-free vulnerability in libssh2's sftp_open() function that can allow a malicious SSH/SFTP server to corrupt client memory and potentially achieve code execution.
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.