CVE-2026-59846 is an information disclosure and command-injection flaw in libssh's ProxyCommand handling. When a ProxyCommand string contains the %r placeholder, libssh expands it using the configured username. If that username is attacker-controlled and contains shell metacharacters, the expanded value can be interpreted by the shell rather than treated as inert data. This can lead to shell metacharacter injection during ProxyCommand execution, causing unintended shell behavior and exposing environment-derived information. The issue affects libssh releases prior to the fixed security versions and was addressed in libssh 0.12.1 and backported to the 0.11 branch in 0.11.5.
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.
2 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.