CVE-2026-60001
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedsshd in OpenSSH before 10.4 does not always honor the minimum authentication delay.
In the news
Third-party coverageSurfaced from public web coverage — external links open in a new tab.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceIn OpenSSH versions before 10.4, the sshd server fails to consistently apply the configured minimum authentication delay between failed login attempts. This allows attackers to perform faster brute-force attacks by circumventing the intended rate-limiting protection that delays subsequent authentication attempts.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 10.4CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Determine installed OpenSSH versionRun 'sshd -V' or check the OpenSSH package version using the system package manager (e.g., 'pkg_info' on OpenBSD)Affected if The installed version is earlier than 10.4 on OpenBSD
-
Locate sshd configuration fileCheck for /etc/ssh/sshd_config or /etc/sshd_configAffected if Configuration file exists and OpenSSH version is below 10.4
-
Inspect authentication rate-limiting settingsSearch the sshd_config file for directives such as 'MaxAuthTries', 'MaxSessions', 'LoginGraceTime', or any custom delay configurations related to authentication attemptsAffected if Rate-limiting is configured and the OpenSSH version is vulnerable (< 10.4)
The environment is affected if OpenBSD OpenSSH version is earlier than 10.4 and authentication delay or rate-limiting is in use, allowing potential faster brute-force attacks.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped10.4
Upgrade OpenSSH to version 10.4 or later. If immediate upgrade is not possible, implement additional authentication controls such as fail2ban, IP allowlisting, or SSH key-based authentication to mitigate brute-force risk.
OpenSSH 10.4
- Upgrade OpenSSH to version 10.4 or later to ensure the minimum authentication delay is properly honored
- After upgrading, verify the sshd configuration includes appropriate authentication delay settings (e.g., MaxAuthTries, LoginGraceTime)
- Test the authentication mechanism to confirm delay is enforced between failed login attempts
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-60001 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-60001 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data