Accelerated brute-force attempts via skipped authentication delay
Published Jul 8, 2026 · Updated Jul 8, 2026
Authentication throttling failure in OpenSSH sshd before 10.4 allows remote attackers to accelerate repeated login attempts. GSSAPI and keyboard-interactive paths failed to apply the common minimum-delay handling, so some failed requests returned before the intended per-user delay elapsed. The server must expose an affected authentication path; the shorter failure cycle facilitates online brute-force attempts without directly disclosing credentials.
Summary
What happened
Authentication throttling failure in OpenSSH sshd before 10.4 allows remote attackers to accelerate repeated login attempts. GSSAPI and keyboard-interactive paths failed to apply the common minimum-delay handling, so some failed requests returned before the intended per-user delay elapsed. The server must expose an affected authentication path; the shorter failure cycle facilitates online brute-force attempts without directly disclosing credentials.
The record
- CVE
- CVE-2026-60001
- Published
- Jul 8, 2026
- Updated
- Jul 8, 2026
- Vendor
- OpenBSD Project
- Product
- OpenSSH
- Classifications
- CWE-770, T1110.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 8, 2026CVE publishedPublication date reported by the CVE source.
- Jul 8, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <10.4
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo