CVE-2026-60001VulnerabilityPublished 30 Sep 2026Updated 29 Oct 2026

Red Hat Security Advisory: openssh security update

Affects Red Hat opensshSource GCVE Database

Compare

Authoritative record:CVE-2026-60001· Medium 6.5

Not known to be exploited · CVSS 6.5 Medium : upgrade Red Hat openssh to 10.4 when convenient.

Data as of 30 Oct 2026, 01:17 UTC

CVSS 3.1 base score

6.5Medium

How severe the flaw is on the 0–10 CVSS scale.

Patch: Available – fixed in 10.4

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: Low
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 8 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade OpenSSH to 10.4.

Affected software

Product	Affected	Fixed in
OpenBSDOpenSSH	Affected <10.4	Fixed in 10.4

AI-suggested

Red Hat has released fixed packages for OpenSSH in Red Hat Enterprise Linux 9. Users should apply the update to version 9.9p1-12.el9_8 or later as provided by Red Hat to remediate this vulnerability. Refer to the Red Hat advisory and article https://access.redhat.com/articles/11258 for detailed update instructions. No additional mitigation is required beyond applying the official update.

Description

A security update for OpenSSH addresses a vulnerability (CVE-2026-60001) that allows brute-force attacks due to insufficient authentication delay. This issue affects OpenSSH implementations in Red Hat Enterprise Linux 9 and related variants. The vulnerability is rated as moderate severity by Red Hat Product Security. A fixed package is available in Red Hat Enterprise Linux 9.8. No public exploit or in-the-wild exploitation has been reported.

Impact

The vulnerability enables attackers to perform brute-force attacks more effectively against OpenSSH servers due to insufficient delay between authentication attempts. This could potentially allow unauthorized access if other security controls are weak. However, no active exploitation has been reported, and the severity is considered moderate.

Summary

The vulnerability identified as CVE-2026-60001 in OpenSSH involves insufficient authentication delay, which facilitates brute-force attacks. This flaw affects OpenSSH versions included in Red Hat Enterprise Linux 9 and its extended update support versions. Red Hat has released an update (openssh-9.9p1-12.el9_8) that addresses this issue. The advisory rates the security impact as moderate and provides detailed package updates for various architectures. No CVSS score is provided in the advisory, but the impact is described as moderate.

CWE-307Improper Restriction of Excessive Authentication Attempts (opens in a new tab)
Base weaknessOWASP Top 10 A07:2025: Authentication Failures (opens in a new tab)
The product does not implement sufficient measures to prevent multiple failed authentication attempts within a short time frame.
Architecture and Design
Common protection mechanisms include: Disconnecting the user after a small number of failed attempts; Implementing a timeout; Locking out a targeted account; Requiring a computational task on the user's part.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
OWASP Cheat Sheets
Authentication (opens in a new tab)
Transport Layer Protection (opens in a new tab)
TLS Cipher String (opens in a new tab)
OWASP ASVS 4.0.3
V2.2.1 (opens in a new tab)
V2.8.5 (opens in a new tab)
V2.8.4 (opens in a new tab)
Attack patterns
Dictionary-based Password Attack (opens in a new tab)
Password Brute Forcing (opens in a new tab)
Password Spraying (opens in a new tab)
Credential Stuffing (opens in a new tab)
Use of Known Kerberos Credentials (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 30 Oct 2026, 01:17 UTC

WeaknessesCWE-307

Technical details

References

Community reviews

Related threats