
Alpine Linux users and administrators running OpenSSH on musl-based systems are being urged to patch a newly disclosed authentication flaw that can let an unauthenticated attacker log in to accounts that should not accept a password at all. The vulnerability, tracked as CVE-2026-123158 and nicknamed sshole, affects a narrow set of configurations, but researchers say it is already being exploited in the wild.
How the OpenSSH authentication flaw works
The bug stems from the way OpenSSH handles password checks when the underlying crypt() call is provided by musl. On affected systems, a password longer than 256 bytes causes musl to return an error value of an asterisk. That same character is also used in Linux /etc/shadow entries to mark an account as having no usable password.
OpenSSH then misinterprets that returned asterisk as a valid match and allows the login. According to the technical explanation published by security researcher Ozgun Kultekin at Wakefield, the flaw can be triggered with any password between 257 and 1,024 characters long under the right conditions.
Which systems are exposed
The vulnerability does not apply broadly to every Linux host running SSH. The affected server must meet several specific conditions at once:
- It must run OpenSSH earlier than version 10.6p2.
- It must be built against musl rather than glibc.
- It must operate without PAM.
- It must have at least one account using a SHA-256 or SHA-512 password hash.
- It must also have an account whose shadow entry is marked with an asterisk.
Alpine Linux is the best-known distribution in scope because it uses musl and, by default, does not enable PAM in OpenSSH. Other musl-based environments such as OpenWrt, Buildroot and Yocto may also be affected if they use the same configuration. Systems using glibc, PAM, Dropbear or OpenBSD are not affected, according to the report.
Why Alpine Linux stands out
For Alpine users, the risk is especially important because the distribution is common in containers, cloud images and embedded deployments. The report notes that on Alpine’s official AWS and Azure images, the default alpine user is passwordless and can use doas without a password, which means a successful login can lead directly to root privileges.
That makes the flaw more than a theoretical authentication issue. A compromised SSH service on an internet-facing Alpine system could hand an attacker access to a high-privilege account in seconds.
How the bug went unnoticed
Kultekin traced the problem to two musl changes made in 2012. One replaced the NULL error return from crypt() with an asterisk; the other introduced a 256-byte limit to SHA-512 password hashing, causing longer inputs to produce an error. In combination, those changes created a return value that OpenSSH could mistake for a legitimate password hash.
The OpenSSH side of the issue comes from a 2016 workaround for CVE-2016-6210, a timing attack that could reveal whether a username existed. To keep login timing similar for valid and invalid users, OpenSSH reused the salt from another account and hashed the supplied password anyway. That logic also applied to real accounts whose shadow entry contained an asterisk.
Kultekin said the issue remained hidden for roughly a decade because the vulnerable combination was uncommon in testing. OpenSSH is typically tested on OpenBSD and glibc-based systems, while many Linux distributions route authentication through PAM, which does not call crypt() for asterisk entries in the same way.
Active exploitation adds urgency
The disclosure has already drawn the attention of threat actors. The report says researchers are seeing exploitation in the wild, including activity linked by GreyNoise to honeypots in Southeast Asia. GreyNoise is tracking one group as GT10, which reportedly deploys a backdoor supporting shell commands, reconnaissance and persistence.
Dan Goodin of Ars Technica reported that WatchTowr tied the activity to botnets and cryptocurrency operations, while Previdian logged 20 exploitation attempts from 13 IP addresses in nine countries. The U.S. Cybersecurity and Infrastructure Security Agency added CVE-2026-123158 to its Known Exploited Vulnerabilities catalog on 9 November, according to Hackread.
What administrators should do now
OpenSSH 10.6p2 contains the fix. For teams that cannot patch immediately, the recommended short-term mitigation is to disable password authentication by setting PasswordAuthentication no in the SSH server configuration and restarting sshd.
Kultekin also recommends checking authentication logs for signs that an account with no password accepted a password. The project has published a detection and background repository to help operators investigate exposure.
Administrators should review whether their SSH servers are built against musl, whether PAM is disabled, and whether shadow entries include asterisk-locked accounts. Those checks matter not only for Alpine Linux servers, but also for Alpine-based containers, embedded systems and custom musl builds that may not be obvious in inventory scans.
Vendor response and scope of impact
Some major vendors have said they are not affected. Red Hat said its products do not meet the required combination of musl and no PAM. Amazon likewise marked Amazon Linux 2 and Amazon Linux 2023 as not affected.
Even so, the issue remains significant for organisations that manage mixed Linux estates. Internet-facing SSH services are common targets, and the narrowness of this bug does not reduce its impact on systems that do match the vulnerable profile.
The vulnerability was publicly disclosed on 5 November, and exploitation reports followed within days. For operators running Alpine Linux or other musl-based SSH deployments, the immediate priority is to patch OpenSSH, restart the service and remove password authentication wherever it is not needed.
Source: Original report
Was this helpful?
Explore more: Application Audit & Review More Cybersecurity Tech News
Last Modified: November 16, 2026 at 10:33 pm
2 views

