● CVE WATCHLIST CVE-2026-84869 ConnectWise ScreenConnect CVE-2026-123039 Check Point Multiple Products CVE-2026-123158 OpenBSD OpenSSH CVE-2026-19868 SonicWall SonicOS SSLVPN CVE-2026-109618 PHP Group PHP CVE-2026-109619 PHP Group PHP

Hackers Exploit OpenSSH SSHole Vulnerability to Gain Root Access on Passwordless Systems

At a glance

CVE
CVE-2026-123158
Product
OpenBSD OpenSSH
Severity
8.1 · High (CVSS 3.1)
Status
Actively exploited · CISA listed 9 Nov 2026
Ransomware use
Not reported
Patch
Available
Weakness
CWE-394
Exploit likelihood (30 days)
18.9%

Live data, updated 3 seconds ago, from NVD, CISA KEV and FIRST EPSS.

Hackers successfully exploited the SSHole authentication bypass vulnerability in OpenSSH, gaining unauthorized access to vulnerable systems shortly after the flaw’s disclosure on November 5, 2026. This critical vulnerability allows attackers to sign into accounts that have no password set, transforming a logic bug into a severe remote access vector.

The vulnerability, identified as CVE-2026-123158, specifically affects Linux systems running OpenSSH compiled with the musl C library while Pluggable Authentication Modules (PAM) are disabled. This configuration is present in the default OpenSSH server setup for Alpine Linux. The flaw was discovered by researcher Özgün Kültekin and subsequently reported to OpenSSH, leading to the release of patches, including OpenSSH 10.6p2 and Alpine Linux updates, on November 5, 2026.

The technical mechanism enabling this attack involves submitting an oversized password, which must be between 257 and 1,024 bytes long. The issue stems from a logic error where the sshd daemon, when running on musl, interprets the failure of the password-hashing operation—which returns an asterisk (*) when a password exceeds 256 bytes—as a successful authentication match against the account’s stored asterisk password hash. This misinterpretation permits the unauthorized login.

The speed of the attack was notable; following the vulnerability’s disclosure on November 5, 2026, hackers were observed successfully exploiting the flaw within hours, with successful exploitation recorded by the following day. This rapid exploitation timeline highlights the immediate danger the flaw posed to exposed services.

It is crucial to understand the specific conditions for exploitation. Successful attacks require the presence of at least one account configured with an asterisk (*) as its password hash, in addition to at least one other account possessing a real SHA-256 or SHA-512 password hash. The vulnerability does not permit attackers to bypass passwords on accounts that are protected by valid password hashes.

Security analysis has assigned the vulnerability a CVSS score of 8.1, classifying it as a high-severity risk. Organizations utilizing OpenSSH on musl-based environments, particularly those with accounts configured without passwords, must apply the necessary patches immediately to mitigate this threat. The flaw is a logic bug, not a memory corruption issue, and arises from a design decision made previously to address a username enumeration vulnerability.

Sources: