CVE-2026-60000 openssh vulnerability
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.
Quick answer
openbsd openssh should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.
Who is affected
Affected versions
- Review vendor advisory for affected versions.
Fixed versions
- Apply the latest vendor-supported patched version.
How to fix it
CVE-2026-60000 affects sshd authentication throttling and resource handling in OpenSSH versions before 10.4. The practical risk is remote resource consumption when GSSAPIAuthentication is enabled and MaxAuthTries is not applied as intended. Prioritize internet-facing SSH servers, bastion hosts, and systems where GSSAPIAuthentication is enabled. OpenSSH fixed this issue in OpenSSH 10.4 and portable OpenSSH 10.4p1, and downstream operating-system vendors may ship the same fix as a backported package update. Patch quickly, then review SSH configuration and logs for any activity that would have relied on the vulnerable behavior.
- Inventory OpenSSH client and server packages across Linux, BSD, macOS, network appliances, containers, bastion hosts, CI runners, and administrative workstations.
- Identify systems running OpenSSH before 10.4 or portable OpenSSH before 10.4p1, including vendor-backported packages that may keep older version strings.
- Upgrade to OpenSSH 10.4/10.4p1 or the operating-system vendor package that explicitly includes the July 2026 OpenSSH security fixes.
- Disable GSSAPIAuthentication unless needed, enforce rate limiting at the network edge, and use PerSourcePenalties or equivalent controls while patching.
- Restart affected sshd services and refresh long-running base images, golden images, containers, and automation hosts so they use the patched binaries.
- Review authentication logs for high-rate failures, GSSAPI attempts, and repeated source addresses before and after the patch.
- If suspicious SSH activity is found, preserve logs, rotate impacted credentials and host keys where appropriate, and rebuild exposed systems when integrity cannot be trusted.
Scan now. Google sign-in is only needed to unlock fix guidance.
Verify the fix
- Confirm each host reports OpenSSH 10.4/10.4p1 or a vendor package changelog that includes the relevant CVE fix.
- Confirm sshd was restarted after package installation and that no stale vulnerable sshd process remains active.
- Confirm authentication delay, MaxAuthTries, and source-penalty behavior match policy after the patched OpenSSH package is deployed.
- Review vulnerability-management and package-inventory output to confirm the affected CVE is closed or explicitly marked fixed by vendor backport.
- Document patched package versions, restart evidence, configuration changes, and residual exceptions, then rerun Fixnx or the relevant vulnerability scan where applicable.
Related categories
Trusted references
FAQ
What is affected by CVE-2026-60000?
openbsd openssh should be checked against the vendor advisory and trusted references linked on this page.
What should I fix first?
Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.
How do I confirm the fix worked?
Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.
How are Fixnx security risk categories chosen?
Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.