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.
CVE-2026-60000
Score 3.7 from GitHub Security Advisory (severity: LOW) published 2026-07-08. NVD baseline CVSS 7.5; sources differ by 3.8.
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 7.5
- EG Score
- 3.7(medium)
- EPSS
- 32.8%
- KEV
- Not listed
Published
July 8, 2026
Last Modified
July 9, 2026
Advisory Details (3)
Auto-updated Jul 9, 2026oss-security - Announce: OpenSSH 10.4 released
https://www.openwall.com/lists/oss-security/2026/07/06/5'Announce: OpenSSH 10.4 released' - MARC
https://marc.info/?l=openssh-unix-dev&m=178333966933090&w=2Vendor Advisories for CVE-2026-60000(2)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
- CVE-2026-60000Microsoft Security Response Center (MSRC)Low
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.
- GHSA-76jm-35gr-hwcmGitHub Security AdvisoriesLow
sshd in OpenSSH before 10.4 allows remote attackers to cause a denial of service (resource...
Patch Availability(1)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| redhat | openssh-main-10.4p1-1.hum1 | 2026-07-09 | redhat |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
All Vendor Advisories
(1)
Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.
Data Freshness Timeline
(refreshed 13× in last 7d / 13× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-10 21:59 UTCEG score recompute
- 2026-07-10 21:59 UTCVendor advisory
- 2026-07-10 21:59 UTCGHSA enrichment
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-09 17:00 UTCNVD updateCVSS v3 → 7.5 · severity → HIGH
- 2026-07-08 15:16 UTCEPSS rescore
- 2026-07-08 15:16 UTCEPSS rescore
- 2026-07-08 00:55 UTCEG score recompute
- 2026-07-08 00:55 UTCMITRE cvelistV5first tracked
Related CVEs(same vendor + same CWE)
Same vendor
10 shownredhat
Frequently asked(5)
What is CVE-2026-60000?
When was CVE-2026-60000 disclosed?
Is CVE-2026-60000 actively exploited?
What is the CVSS score of CVE-2026-60000?
How do I remediate CVE-2026-60000?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-60000
Is Your Infrastructure Affected by CVE-2026-60000?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.