Alpine Linux Users Urged to Patch OpenSSH Authentication Flaw
The root mechanism behind the flaw lies in the interaction between OpenSSH password validation routines and the underlying musl crypt() implementation.
By Dillip Chowdary • Nov 16, 2026 • Source: InfoQ

At a glance
- Product
- OpenSSH
- Vulnerability ID
- CVE-2026-123158
- Patched version
- 10.6p2
- Disclosure date
- 5 November 2026
- Catalog addition
- 9 November 2026
- Input length limit
- 257 to 1,024 characters
In this post
Security teams across Linux infrastructure are rushing to deploy patches following the disclosure of an authentication vulnerability in OpenSSH that allows unauthenticated attackers to log directly into passwordless accounts. The vulnerability, designated as CVE-2026-123158 and dubbed *sshole, specifically compromises Linux systems running OpenSSH built with the musl C library when Pluggable Authentication Modules are absent, according to InfoQ's report. Active exploitation began within days of the initial 5 November public disclosure, prompting immediate remediation alerts across the DevOps and cloud administration sectors.
This dispatch details the technical mechanics behind the flawed password evaluation, the specific environmental conditions necessary for compromise, affected operating systems, observed threat actor activity in the wild, and concrete steps required to secure internet-facing servers. Systems running Alpine Linux, particularly instances deployed across public clouds, face immediate exposure to remote takeover. Engineering teams operating lightweight container base images, custom embedded builds, or appliances running without centralized authentication must evaluate their exposed SSH endpoints immediately.
01Musl error code and asterisk evaluation
The root mechanism behind the flaw lies in the interaction between OpenSSH password validation routines and the underlying musl crypt() implementation. When a user supplies an input string longer than 256 bytes on a musl-based system, the library aborts processing and generates an error return value. Instead of returning a standard null indicator, musl outputs a single asterisk character.
Standard Linux systems place an asterisk inside the /etc/shadow file to designate disabled or locked accounts that should never accept interactive password logins. Because OpenSSH interprets the returned single asterisk from musl as a valid hash comparison against the target account's shadow entry, it registers a matching string. The daemon then verifies the authentication attempt as successful and immediately admits the remote attacker into the target session.
Wakefield security researcher Ozgun Kultekin discovered the anomaly after compiling OpenSSH across multiple library environments and systematically testing roughly 17,600 unusual login sequences. The flaw went unnoticed for over a decade because upstream OpenSSH test harnesses evaluate OpenBSD and GNU C Library environments, while standard Linux enterprise distributions route authentication requests through PAM layers that handle asterisk shadow fields differently.
02Legacy commits and timing mitigations
Kultekin traced the technical origins of the flaw to two specific code changes committed to the musl library back in 2012. The first commit altered the crypt() error output behavior, replacing the original NULL pointer return with an asterisk. The second commit introduced a strict 256-byte ceiling for SHA-512 cryptographic hashing operations, ensuring that any input exceeding that length triggers an error state.
The server-side vulnerability was sealed in 2016 when OpenSSH introduced a security mitigation for CVE-2016-6210, an issue where timing differences allowed attackers to enumerate valid usernames. To equalize processing latency across existent and nonexistent users, OpenSSH began borrowing salt strings from sibling accounts to compute dummy hashes when examining invalid requests. That timing defense applied indiscriminately to accounts marked with an asterisk inside the shadow database.
Together, these historical design decisions produced an unintended authentication bypass path when specific configurations converged. A remote connection need only transmit a payload between 257 and 1,024 characters to force musl into returning an asterisk. Because the server treats the borrowed salt and resulting error symbol as an intentional match, the authentication logic succeeds without cryptographic verification.
03Narrow requirements and Alpine exposure
Advertisement
Tech Pulse Daily
Get tomorrow's pulse first
Join engineers who read Tech Pulse before stand-up. Free, weekday mornings.
Exploiting the flaw requires a precise combination of architectural dependencies and local system configurations. The underlying operating system must execute OpenSSH versions prior to 10.6p2, rely on the musl C library instead of glibc, and operate with PAM authentication disabled entirely. Furthermore, the local shadow database must host at least one account configured with a SHA-256 or SHA-512 password hash alongside another separate account carrying an asterisk in its password field.
| Distribution or Component | Status | Architectural Reason |
|---|---|---|
| Alpine Linux | Vulnerable | Uses musl by default without PAM in default OpenSSH configuration |
| OpenWrt | Potentially Vulnerable | Employs musl library when built with OpenSSH instead of Dropbear |
| Buildroot / Yocto | Potentially Vulnerable | Exposed when configured with musl and standalone OpenSSH builds |
| Red Hat Enterprise Linux | Not Affected | Uses glibc and routes authentication through system PAM |
| Amazon Linux 2 / 2023 | Not Affected | Relies on glibc and PAM integration for access control |
| OpenBSD | Not Affected | Upstream system does not run the musl C library |
Note: Systems relying on Dropbear SSH or glibc-based authentication are not affected by CVE-2026-123158 under any configuration.
On official Alpine Linux cloud images published for Amazon Web Services and Microsoft Azure, the operating system provisions a default alpine account configured without an interactive password. That account possesses permission to execute administrative commands via doas without entering authentication credentials. An attacker targeting the default cloud user can leverage the bypass to execute arbitrary code and seize complete root control within seconds of establishing a network socket.
04Active botnet exploitation and threat actors
Telemetry from internet monitoring firms confirms that multiple distinct adversary clusters began exploiting the vulnerability across public networks shortly after release. Threat monitoring firm GreyNoise observed intrusion attempts directed at honeytokens and honeypots stationed throughout Southeast Asia. The activity was attributed to an adversary tracking cluster designated as GT10, which deploys automated backdoor payloads capable of reconnaissance, command execution, and long-term host persistence.
Security research collective watchTowr correlated live scan patterns with expanding botnet recruitments and cryptocurrency mining operations targeting exposed micro-instances. Threat intelligence service Previdian documented 20 verified exploitation sequences originating from 13 independent IP addresses distributed across nine separate countries. In response to confirmed exploitation telemetry, the United States Cybersecurity and Infrastructure Security Agency added CVE-2026-123158 to its Known Exploited Vulnerabilities catalog on 9 November.
Adversaries are actively targeting internet-facing virtual machines, microservices, and management bastions using automated credential probes. Because the payload requirements involve simply transmitting an arbitrary string of 257 characters or more to disabled system accounts, network scanners can triage reachable endpoints with minimal bandwidth overhead. Forensic teams monitoring affected subnets report persistent attempts to establish unauthenticated interactive shells across exposed infrastructure boundaries.
05Server remediation and verification steps
The OpenSSH development team released version 10.6p2 to correct the evaluation flaw and neutralize improper musl error handling. Systems administrators managing musl environments, custom lightweight Linux distributions, or Alpine containers must update package repositories and upgrade existing installations immediately. Organizations that cannot immediately deploy package upgrades must apply configuration workarounds to isolate the network attack surface.
- Audit host libraries inspect system binaries to determine whether the running OpenSSH service links against musl or glibc.
- Review account entries examine /etc/shadow to identify locked or service accounts that display an asterisk within their credential field.
- Disable password access configure the PasswordAuthentication directive to no inside the sshd_config file to prevent interactive password evaluations.
- Restart daemon execute service restart commands to load the updated configuration files and terminate existing unauthenticated negotiation states.
- Inspect audit logs parse authentication journal entries for unexpected successful password logins against accounts configured with asterisk shadow entries.
The OpenSSH project published a dedicated detection and background repository to assist engineering teams with log analysis and footprint identification. Removing interactive password negotiation completely eliminates the vulnerability surface, ensuring that only cryptographically signed SSH public keys can complete connection negotiations. For internet-facing systems, disabling password authentication and applying the latest package revision ensures complete defense against ongoing automated exploitation campaigns.
Frequently asked questions
What causes the authentication bypass in CVE-2026-123158?
When OpenSSH passes a password longer than 256 bytes to the musl crypt() function, the library returns an asterisk error value. OpenSSH treats this asterisk as a match against shadow entries configured with an asterisk for passwordless accounts and permits the login.
Which Linux distributions are affected by the OpenSSH flaw?
Alpine Linux is the most prominent affected distribution because it combines the musl C library with an OpenSSH setup that lacks PAM. Other musl-based distributions like OpenWrt, Buildroot, and Yocto are also vulnerable if configured without PAM, while glibc-based systems such as Red Hat and Amazon Linux are not affected.
How can administrators fix or mitigate CVE-2026-123158?
Administrators should immediately upgrade to OpenSSH 10.6p2 and restart the service. If upgrading is not immediately possible, operators should set PasswordAuthentication no in the SSH server configuration file and reload the daemon.
Why are official Alpine Linux cloud images at severe risk?
Official Alpine images on AWS and Azure include a default alpine user that has an asterisk in its password field and can run doas without a password. Attackers exploiting the bug can authenticate to this account using a long password string and gain root privileges within seconds.
Sources
Author
Dillip Chowdary
Writes Tech Bytes coverage of AI, engineering, and the tools that actually ship. Editor of Tech Pulse Daily.
Related on Tech Bytes
Advertisement