OpenSSH has rolled out emergency patches to address a high-severity authentication bypass vulnerability that allows unauthorized attackers to log into targeted systems using specially crafted, very long passwords. Tracked as CVE-2026-123158 and carrying a critical CVSS score of 8.1, the security defect—dubbed "SSHole" by security researchers—specifically impacts the OpenSSH server daemon, known as sshd, on Linux distributions that utilize the musl libc implementation with the Pluggable Authentication Module (PAM) disabled.
The root cause of the vulnerability stems from a misinterpretation of whether a string is intended to be a password hash within the underlying system code. This logic flaw allows malicious actors to successfully access specific user accounts by presenting any password composed of between 257 and 1,024 characters. While standard security practices dictate that certain critical accounts, such as the administrative root account, should never accept a password authentication method directly, various lightweight Linux distributions configured with musl libc—including Alpine Linux, OpenWrt, Buildroot, and Yocto—do permit this under specific conditions, according to findings shared by Wakefield security researcher Özgün Kültekin.
Addressing the nature of the bug, OpenSSH developer Damien Miller clarified that the defect itself does not strictly reside within the core codebase of sshd, but can nonetheless be successfully exploited via the server daemon. Swift remediation was prioritized by the development team, with official fixes incorporated into the newly released OpenSSH version 10.6p2.
Explaining the rapid turnaround time for the security advisory, Miller highlighted a shifting reality in modern cybersecurity where automated tools accelerate threat actor capabilities. "We are making this release as fast as possible because we have recently observed multiple cases of rapid bug rediscovery by AI agents, sometimes within hours, and so now consider long embargo periods to be a dangerous practice that primarily benefits attackers," Miller noted in a public statement.
Following the disclosure, distributions such as Alpine Linux issued urgent advisories on Thursday, urging system administrators to immediately apply the official OpenSSH patches and restart the sshd service to replace the running daemon. Alternatively, administrators were advised to completely disable password-based logins and restart the service as a temporary mitigation measure if immediate patching is not feasible.
Detailing the exact prerequisites required for a successful attack, Alpine Linux warned that the exploit vector is remarkably straightforward under the right conditions. An attacker requires knowledge of the name of an account whose password field is set to a single asterisk character, denoting an account with no active password set, which is standard behavior for key-only authentication accounts. Furthermore, the targeted machine must have at least one other local account configured with a password hash starting with either a $5$ or a $6$ identifier.
Since version 3.16, Alpine Linux has utilized an asterisk to secure the root account, while the presence of $5$ or $6$ in password hashes indicates whether the SHA-256 or SHA-512 crypt implementation was used by the system. When these conditions are met, an attacker who can reach the open SSH port of a machine can log in successfully without knowing any valid password. Security advisories emphasize that the attack requires only a single connection attempt, works consistently every time, and necessitates no iterative retries or brute-force guessing phases.
Affected Alpine Linux deployments are specifically those running OpenSSH without PAM enabled, operating with password authentication turned on, hosting an account with an asterisk password field—such as root, a key-only user created via adduser without an explicit password, the default alpine user in official tiny-cloud images, or a user provisioned from a directory service through musl-nscd—and featuring at least one local account utilizing a $5$ or $6$ password hash. According to Alpine Linux security notices, the vulnerability impacts every checked release spanning versions 3.21 through 3.24, the rolling edge branch, as well as older releases that have reached end-of-life and no longer receive regular maintenance updates, ranging from version 3.16 to 3.20.
Security experts emphasize that while no confirmed reports of active exploitation in the wild have been documented at the time of disclosure, the public availability of technical details and the simplicity of the attack vector mean that automated scanning and exploitation attempts are virtually guaranteed to materialize rapidly.
Expressing concern over the widespread exposure of SSH services globally, Detectify co-founder and principal security researcher Fredrik Almroth pointed out the scale of potential targets. "We haven’t seen any reports of exploitation yet, but the details are public, and the attack is simple, so I expect scanning to start within hours. Finding targets is very easy. Shodan lists around 22 million systems with SSH open on port 22, and the real number is higher because Shodan doesn’t see everything. Only some of those run Alpine, but each attempt is a single connection, so an attacker can afford to try all of them," Almroth explained.
Echoing these urgent sentiments, WatchTowr head of threat intelligence Jake Knott warned that malicious automated tooling would likely waste little time weaponizing the flaw. "We’d be extremely surprised if we didn’t see SSH brute-forcers attempting this by the weekend. It’s virtually free to try and an easy win if it works. If your organization is affected, update to the latest version where possible, and disable password-based authentication as a temporary mitigation if you can’t," Knott advised.

