dbcve.org
OpensshApplication · OpenBSD

CVE-2026-60000

HIGH · 7.5 CVSS v3.1 Published 2026-07-08
Fix available
A fix is available. Upgrade to 10.4 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click 6 weeks old

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 · unedited
sshd in OpenSSH before 10.4 allows remote attackers to cause a denial of service (resource consumption from excessive authentication attempts) because MaxAuthTries was mishandled for GSSAPIAuthentication.

In the news

Third-party coverage
Trending covered by 1 outlet this week · latest 1mo ago

Surfaced 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 · high confidence

In OpenSSH versions before 10.4, the MaxAuthTries limit was not properly enforced when GSSAPIAuthentication was enabled, allowing remote attackers to make unlimited authentication attempts without triggering the account lockout or connection limits that MaxAuthTries is designed to provide.

MitigationUpgrade to OpenSSH 10.4 or later, or disable GSSAPIAuthentication in sshd_config if not required, as the fix properly applies MaxAuthTries limits to GSSAPI 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
OpensshApplication
Affected:< 10.4

CVSS 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
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed OpenSSH version
    Run 'sshd -v' or 'ssh -V' to determine the version number, or check the OpenSSH package version via the system package manager
    Affected if Version is earlier than 10.4 (for example, 10.3, 10.2, etc.)
  2. Verify GSSAPIAuthentication is enabled
    Inspect /etc/ssh/sshd_config for the line 'GSSAPIAuthentication' - if present and set to 'yes', or if the directive is absent (defaulting to yes in some configurations), the vulnerable code path is active
    Affected if GSSAPIAuthentication is set to 'yes' or is not explicitly disabled
  3. Confirm MaxAuthTries configuration
    Check /etc/ssh/sshd_config for 'MaxAuthTries' directive - note the configured value if present
    Affected if MaxAuthTries is set to any value AND GSSAPIAuthentication is enabled, because the limit would not be enforced in affected versions
  4. Check sshd service accessibility
    Verify that sshd is running and accessible on the network (for example, check if port 22 is open and listening)
    Affected if The sshd service is exposed to network access, as this is required for remote exploitation

You are affected if you run OpenSSH versions before 10.4 on OpenBSD, have GSSAPIAuthentication enabled in sshd_config, and have MaxAuthTries configured - the authentication attempt limit would not be enforced for GSSAPI authentication attempts.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 10.4 or later
Fixed in 10.4
Interim mitigation

Upgrade to OpenSSH 10.4 or later, or disable GSSAPIAuthentication in sshd_config if not required, as the fix properly applies MaxAuthTries limits to GSSAPI authentication attempts.

Recommended fix Moderate confidence

OpenSSH 10.4

  1. Verify the current OpenSSH version using: sshd -V or ssh -V
  2. Backup the current SSH configuration files in /etc/ssh/
  3. Update the system package repository
  4. Upgrade OpenSSH to version 10.4 or later using the system's package manager (e.g., apt-get update && apt-get install openssh-server for Debian/Ubuntu, or yum/dnf for RHEL-based systems)
  5. Verify the new version is installed: sshd -V
  6. Test SSH connectivity in a new terminal session before closing the current session
  7. Ensure MaxAuthTries is properly configured in /etc/ssh/sshd_config (recommended value: 3-6)
  8. Restart the SSH daemon: systemctl restart sshd or systemctl restart ssh
Caveat Upgrading OpenSSH is generally safe but could cause issues if client/server version mismatch occurs; always test in a non-production environment first and maintain console/physical access for recovery

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Openssh Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,970
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-60000 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-60000 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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