Quick answers
- Is CVE-2026-60001 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-60001 being exploited in the wild.
- How severe is CVE-2026-60001?
- Medium severity, with a CVSS score of 6.5, published 8 July 2026.
- Which products and versions are affected?
- OpenBSD Openssh before 10.4.
- Is there a fix for CVE-2026-60001?
- A patch was published on 2026-07-06: OpenSSH 10.4 released with fix. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-60001 attacked?
- It is attacked over the network, in an operating system.
- Am I affected by CVE-2026-60001?
- 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 vulnerability exists in OpenSSH's sshd component where the minimum authentication delay is not consistently enforced across all authentication paths. This flaw, classified under CWE-770 (Allocation of Resources Without Limits or Throttling), allows a remote, unauthenticated attacker to perform authentication attempts more rapidly than the configured security policy should allow. While it does not directly grant access, it undermines rate-limiting protections designed to mitigate brute-force or dictionary attacks. 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 fix.
- 2026-07-08: disclosed: CVE-2026-60001 published.