Quick answers
- Is CVE-2026-60002 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-60002 being exploited in the wild.
- How severe is CVE-2026-60002?
- High severity, with a CVSS score of 7.7, published 8 July 2026.
- Which products and versions are affected?
- OpenBSD Openssh before 10.4.
- Is there a fix for CVE-2026-60002?
- A patch was published on 2026-07-06: OpenSSH 10.4 released with security fixes. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-60002 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-60002?
- Check whether you run OpenBSD Openssh at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A use-after-free vulnerability exists in the OpenSSH client (ssh) prior to version 10.4. The flaw is triggered during a post-authentication key re-exchange if the server changes its host key. An attacker controlling a malicious server can exploit this memory corruption issue to potentially achieve remote code execution or cause a denial of service on the client side. The attack requires a network connection but is mitigated by the high complexity of successfully manipulating memory during the re-exchange process. The issue is resolved in OpenSSH version 10.4.
Affected products
- OpenBSD OpenSSH before 10.4
Timeline
- 2026-07-06: patched: OpenSSH 10.4 released with security fixes.
- 2026-07-08: advisory: CVE-2026-60002 published.