Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:LSummary
CVE-2026-60001 is a medium-severity Allocation of Resources Without Limits or Throttling (CWE-770) vulnerability in Openbsd Openssh. Its CVSS base score is 6.5 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Brute Force (T1110); ranked at the 21th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to AC-7 (Unsuccessful Logon Attempts) and SC-7 (Boundary Protection) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-42145
Vulnerability Data
sshd in OpenSSH before 10.4 does not always honor the minimum authentication delay.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise TechniquesAI
Why these techniques?
The vulnerability allows bypassing the intended minimum authentication delay in OpenSSH, which could facilitate brute-force or password-guessing attempts (T1110) by reducing the time between authentication attempts.
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
Mitigating Controls (NIST 800-53 r5) AI
AC-7 enforces configurable thresholds for unsuccessful logon attempts and the associated delay between attempts, directly mitigating the failure of sshd to honor the minimum authentication delay.
SC-7 boundary-protection mechanisms can limit the rate of inbound SSH connections, reducing the impact of an authentication-delay bypass.
SI-4 continuous monitoring can detect anomalous authentication patterns that result from the missing minimum-delay enforcement.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Monitoring capacity and taking action to maintain availability directly reduces unchecked resource allocation.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Baseline comparison of CPU, memory and bandwidth usage helps surface uncontrolled resource allocations before they cause service degradation.
Capacity projections and elasticity measures ensure that allocation requests are bounded and can be throttled, reducing the window in which an attacker can force unbounded resource reservations.
Defining retention periods and deletion schedules for backup copies prevents indefinite accumulation of data on storage media without corresponding resource-management controls.
Architectural redundancy and automatic failover limit the impact of an attacker who forces excessive allocations, because spare capacity can absorb the load until the primary instance recovers.
Documented incident response procedures that include activation of continuity plans and controlled recovery help ensure that resource consumption triggered by an incident is bounded and managed rather than left unbounded.
Mandating tested continuity procedures that preserve or replace resource-limiting controls prevents an attacker from exploiting the absence of throttling mechanisms during an outage.