CVE-2026-60000

HIGHNVD 7.57.5
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 63% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.

Triggered by: NVD CVSS baseline
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: None knownExposed: 0

A fix is available — apply it.

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.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
34(Track)
EG Risk 34/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
37%
KEV
Not listed

Published

July 8, 2026

Last Modified

July 9, 2026

Advisory Details (3)

Auto-updated Jul 9, 2026
No patch confirmed yet.
generic

oss-security - Announce: OpenSSH 10.4 released

https://www.openwall.com/lists/oss-security/2026/07/06/5
generic

'Announce: OpenSSH 10.4 released' - MARC

https://marc.info/?l=openssh-unix-dev&m=178333966933090&w=2

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntussh-askpass-gnome (1:10.2p1-2ubuntu3.4) @ resolute2026-08-30ubuntu
redhatopenssh-main-10.4p1-1.hum12026-07-09redhat

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.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
openssh1:10.0p1-1 ... 1:9.9p2-2 (86 versions)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
openssh1:10.0p1-1 ... 1:9.9p2-2 (75 versions)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
openssh1:10.0p1-7 ... 1:10.4p1-4 (29 versions)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
openssh1:10.0p1-7 ... 1:10.3p1-9 (21 versions)1:10.4p1-1

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 29× in last 7d / 168× 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.

Showing the most recent 100 of 239 total refreshes for this CVE.

  1. 2026-08-30 07:40 UTCEG score recompute
  2. 2026-08-30 07:40 UTCVendor advisory
  3. 2026-08-30 07:40 UTCGHSA enrichment
  4. 2026-08-30 01:22 UTCEPSS rescore
  5. 2026-08-28 21:42 UTCEPSS rescore
  6. 2026-08-27 21:54 UTCEG score recompute
  7. 2026-08-27 21:54 UTCVendor advisory
  8. 2026-08-27 21:54 UTCGHSA enrichment
  9. 2026-08-27 14:25 UTCEPSS rescore
  10. 2026-08-27 01:51 UTCEG score recompute
  11. 2026-08-27 01:51 UTCVendor advisory
  12. 2026-08-27 01:51 UTCGHSA enrichment
  13. 2026-08-26 14:46 UTCEPSS rescore
  14. 2026-08-26 12:56 UTCEG score recompute
  15. 2026-08-26 12:56 UTCVendor advisory
  16. 2026-08-26 12:56 UTCGHSA enrichment
  17. 2026-08-25 13:49 UTCEPSS rescore
  18. 2026-08-25 11:52 UTCVendor advisory
  19. 2026-08-25 11:52 UTCGHSA enrichment
  20. 2026-08-24 23:51 UTCEG score recompute
  21. 2026-08-24 23:51 UTCVendor advisory
  22. 2026-08-24 23:51 UTCGHSA enrichment
  23. 2026-08-24 12:37 UTCEG score recompute
  24. 2026-08-24 12:37 UTCVendor advisory
  25. 2026-08-24 12:37 UTCGHSA enrichment
Show 75 more
  1. 2026-08-24 01:03 UTCVendor advisory
  2. 2026-08-24 01:03 UTCGHSA enrichment
  3. 2026-08-23 13:38 UTCVendor advisory
  4. 2026-08-23 13:38 UTCGHSA enrichment
  5. 2026-08-23 02:24 UTCEG score recompute
  6. 2026-08-23 02:24 UTCVendor advisory
  7. 2026-08-23 02:24 UTCGHSA enrichment
  8. 2026-08-23 00:19 UTCEPSS rescore
  9. 2026-08-22 15:09 UTCVendor advisory
  10. 2026-08-22 15:09 UTCGHSA enrichment
  11. 2026-08-22 03:55 UTCEG score recompute
  12. 2026-08-22 03:55 UTCVendor advisory
  13. 2026-08-22 03:55 UTCGHSA enrichment
  14. 2026-08-21 23:49 UTCEPSS rescore
  15. 2026-08-21 15:23 UTCVendor advisory
  16. 2026-08-21 15:23 UTCGHSA enrichment
  17. 2026-08-21 04:09 UTCEG score recompute
  18. 2026-08-21 04:09 UTCVendor advisory
  19. 2026-08-21 04:09 UTCGHSA enrichment
  20. 2026-08-20 22:55 UTCEPSS rescore
  21. 2026-08-20 15:39 UTCVendor advisory
  22. 2026-08-20 15:39 UTCGHSA enrichment
  23. 2026-08-20 02:09 UTCEG score recompute
  24. 2026-08-20 02:09 UTCVendor advisory
  25. 2026-08-20 02:09 UTCGHSA enrichment
  26. 2026-08-19 17:04 UTCEPSS rescore
  27. 2026-08-19 09:48 UTCVendor advisory
  28. 2026-08-19 09:48 UTCGHSA enrichment
  29. 2026-08-18 22:28 UTCEG score recompute
  30. 2026-08-18 22:28 UTCVendor advisory
  31. 2026-08-18 22:28 UTCGHSA enrichment
  32. 2026-08-18 13:48 UTCEPSS rescore
  33. 2026-08-18 10:53 UTCVendor advisory
  34. 2026-08-18 10:53 UTCGHSA enrichment
  35. 2026-08-17 22:32 UTCEG score recompute
  36. 2026-08-17 22:32 UTCVendor advisory
  37. 2026-08-17 22:32 UTCGHSA enrichment
  38. 2026-08-17 13:47 UTCEPSS rescore
  39. 2026-08-17 08:53 UTCVendor advisory
  40. 2026-08-17 08:53 UTCGHSA enrichment
  41. 2026-08-16 21:39 UTCEG score recompute
  42. 2026-08-16 21:39 UTCVendor advisory
  43. 2026-08-16 21:39 UTCGHSA enrichment
  44. 2026-08-16 14:56 UTCEPSS rescore
  45. 2026-08-16 10:24 UTCEG score recompute
  46. 2026-08-16 10:24 UTCVendor advisory
  47. 2026-08-16 10:24 UTCGHSA enrichment
  48. 2026-08-15 23:11 UTCVendor advisory
  49. 2026-08-15 23:11 UTCGHSA enrichment
  50. 2026-08-15 11:57 UTCEG score recompute
  51. 2026-08-15 11:57 UTCVendor advisory
  52. 2026-08-15 11:57 UTCGHSA enrichment
  53. 2026-08-15 01:30 UTCEPSS rescore
  54. 2026-08-15 00:43 UTCVendor advisory
  55. 2026-08-15 00:43 UTCGHSA enrichment
  56. 2026-08-14 13:29 UTCVendor advisory
  57. 2026-08-14 13:29 UTCGHSA enrichment
  58. 2026-08-14 02:12 UTCEG score recompute
  59. 2026-08-14 02:12 UTCVendor advisory
  60. 2026-08-14 02:12 UTCGHSA enrichment
  61. 2026-08-13 22:00 UTCEPSS rescore
  62. 2026-08-13 14:58 UTCVendor advisory
  63. 2026-08-13 14:58 UTCGHSA enrichment
  64. 2026-08-13 03:44 UTCVendor advisory
  65. 2026-08-13 03:44 UTCGHSA enrichment
  66. 2026-08-12 16:30 UTCEG score recompute
  67. 2026-08-12 16:30 UTCVendor advisory
  68. 2026-08-12 16:30 UTCGHSA enrichment
  69. 2026-08-12 13:51 UTCEPSS rescore
  70. 2026-08-12 05:16 UTCVendor advisory
  71. 2026-08-12 05:16 UTCGHSA enrichment
  72. 2026-08-11 18:02 UTCEG score recompute
  73. 2026-08-11 18:02 UTCVendor advisory
  74. 2026-08-11 18:02 UTCGHSA enrichment
  75. 2026-08-11 06:46 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-60000?
CVE-2026-60000 is a high vulnerability published on July 8, 2026. 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.
When was CVE-2026-60000 disclosed?
CVE-2026-60000 was first published in the National Vulnerability Database on July 8, 2026, with the most recent update on July 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-60000 actively exploited?
CVE-2026-60000 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 63.3% of all scored CVEs.
What is the CVSS score of CVE-2026-60000?
CVE-2026-60000 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-60000?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-60000, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-60000

Explore →

Is Your Infrastructure Affected by CVE-2026-60000?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.