Loading vulnerability…
CVE-2025-15661 is an out-of-bounds heap read vulnerability in libssh2 affecting versions through 1.11.1. The flaw is in the sftp_symlink() function in src/sftp.c, which processes SSH_FXP_NAME responses for SFTP READLINK and REALPATH operations. The vulnerable code fails to validate that sufficient packet buffer data is available before performing a memcpy based on attacker-influenced length information. By sending a crafted SSH_FXP_NAME response with a link_len value larger than the actual packet data, a malicious SSH server or a man-in-the-middle attacker can trigger a heap buffer over-read of up to target_len minus one bytes. The issue was fixed upstream in commit 2dae302.
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.
20 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
High-severity out-of-bounds read vulnerability in libssh2's sftp_symlink() due to insufficient packet buffer size validation, allowing information disclosure via a malicious SSH_FXP_NAME response in SFTP operations.
An additional vulnerability referenced as applicable for remediation alongside the primary libssh2 issue, without further detail.
A vulnerability affecting libssh2, which is compiled into Cargo, and fixed in Rust 1.96.1.
A libssh2 SFTP heap over-read vulnerability mentioned as another flaw to patch alongside CVE-2026-55200.
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.