Skip to content
Alpine Linux Users Urged to Patch OpenSSH Authentication Flaw

Alpine Linux Users Urged to Patch OpenSSH Authentication Flaw

News.Lavx.Hu • November 16, 2026

A vulnerability in OpenSSH, tracked as CVE-2026-123158 and named sshole, lets unauthenticated attackers log in to accounts that should have no usable password on musl-based Linux systems without PAM. Alpine Linux is the most prominent affected distribution, and researchers report active exploitation.

A vulnerability in OpenSSH, tracked as CVE-2026-123158 and named sshole, lets an unauthenticated attacker log in to accounts that should have no usable password. The flaw affects Linux systems running OpenSSH built against the musl C library without PAM. Security researchers report active exploitation.

The bug comes from password checking when musl handles the underlying crypt() call. On an affected system, a password longer than 256 bytes causes musl to return an error value. That value is an asterisk, the same character Linux uses in /etc/shadow to mark an account as having no password. OpenSSH treats the returned asterisk as a match and permits the login.

Exploitation requires several conditions. The server must run OpenSSH before 10.6p2, use musl rather than glibc, and operate without PAM. It must also have at least one account with a SHA-256 or SHA-512 password hash and another account marked with an asterisk in its shadow entry. When those conditions hold, any password between 257 and 1,024 characters can authenticate against the passwordless account.

Alpine Linux is the most prominent affected distribution because it uses musl and its default OpenSSH configuration does not enable PAM. OpenWrt, Buildroot, and Yocto may also be affected where the same configuration applies. Systems using glibc, PAM, Dropbear, or OpenBSD are not affected.

Ozgun Kultekin, a security researcher at Wakefield, published the technical explanation on the sshole website. Kultekin traces the problem to two musl changes made in 2012. The first replaced the NULL error return from crypt() with an asterisk. The second added a 256-byte limit to SHA-512 password hashing, so longer inputs caused an error. Together, the changes produced a value that could be mistaken for a password hash.

The OpenSSH side dates from a 2016 fix for CVE-2016-6210, a timing attack that could reveal whether a username existed. To make responses take a similar amount of time for valid and invalid users, OpenSSH borrowed the salt from another account and hashed the supplied password anyway. That workaround also applied to real accounts whose shadow entry contained an asterisk.

Kultekin says the issue remained unnoticed for a decade because the vulnerable combination was uncommon in testing. Testing covers 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. Kultekin found the bug after building OpenSSH in several configurations and testing 17,600 unusual login attempts.

On Alpine's official AWS and Azure images, the default alpine user is marked as passwordless and can use doas without a password. An attacker who reaches that account can therefore obtain root privileges. Kultekin wrote: "On alpine's official aws and azure images that's the default alpine user, and it has passwordless doas . so it's root."

Kultekin also wrote: "Accounts that should never take a password at all (root, your key-only deploy user, ldap users, the default user on alpine's aws and azure images) take any password longer than 256 characters."

The issue can give unauthenticated access to high-privilege accounts within seconds on affected systems. GreyNoise reported that attackers hit honeypots in Southeast Asia. The group, tracked as GT10, deploys a backdoor that supports shell commands, reconnaissance, and persistence. watchTowr linked the activity to botnets and cryptocurrency operations. Previdian recorded 20 exploitation attempts from 13 IP addresses in nine countries.

The United States Cybersecurity and Infrastructure Security Agency added CVE-2026-123158 to its Known Exploited Vulnerabilities catalog on Nov. 9. Red Hat said its products are not affected because they do not meet the required combination of musl and no PAM. Amazon marked Amazon Linux 2 and Amazon Linux 2023 as not affected.

That does not remove the risk for teams running Alpine-based containers, embedded devices, or custom musl builds. Administrators should look for SSH servers built against musl, check whether PAM is disabled, review shadow entries for asterisk-locked accounts, apply OpenSSH 10.6p2, and restart the service.

OpenSSH 10.6p2 contains the fix. Operators unable to update can disable password authentication by setting PasswordAuthentication no in the SSH server configuration and restarting sshd. Kultekin also advises checking authentication logs for evidence that an account with no password accepted a password. The project published a detection and background repository.

The vulnerability became public on Nov. 5, and exploitation reports followed within days. For organizations with internet-facing SSH services, the immediate action is straightforward: update OpenSSH, restart it, and remove password authentication where it is not needed.

Source : Alpine Linux Users Urged to Patch OpenSSH Authentication Flaw , by Matt Saunders , InfoQ , Nov 16, 2026

Extracted Entities

Attack Types (1)

Companies (2)

Countries (1)

Domains (1)

Malware (1)

Vulnerabilities (1)