CVE-2026-60002 is a use-after-free vulnerability in the ssh client in OpenSSH versions before 10.4. The memory-safety flaw can occur when an SSH server changes its host key during key re-exchange. The condition occurs only on the client side and can cause denial of service, including a potential client crash. The affected function and detailed memory-management failure are not specified.
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.
37 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A client-side use-after-free in OpenSSH ssh can occur when a server changes its host key during key re-exchange. This vulnerability is the stated source of the plugin's CVSS score.
A client-side use-after-free can occur when an SSH server changes its host key during key re-exchange. This CVE is identified as the source of the plugin's severity scoring.
A client-side use-after-free can occur in OpenSSH ssh when a server changes its host key during key re-exchange. The plugin identifies this CVE as its CVSS score source.
A client-side use-after-free vulnerability in OpenSSH ssh, triggered when a server changes its host key during key re-exchange. The plugin identifies this CVE as its CVSS v2 score source. Updated EulerOS openssh packages are available; the description does not establish a specific exploitation outcome beyond the memory-safety flaw.
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.