Description
On November 5, 2026, Alpine Linux published a security advisory warning users about a password authentication bypass affecting its OpenSSH server package.
The vulnerability was discovered by security researcher Özgün Kültekin of Wakefield and reported privately to the OpenSSH security team before public disclosure.
The flaw is associated with a combination of OpenSSH password verification logic and the behavior of musl libc's password-hashing function.
Under specific conditions, an attacker who can reach the SSH service may authenticate to an account whose password field contains *, even though that account is not configured to accept password-based authentication.
The issue is particularly concerning for Alpine systems because the standard openssh-server package is built without PAM, and password authentication is enabled by default unless administrators change the configuration.
The vulnerability has been addressed in OpenSSH 10.6p2, with distribution-specific fixes also published by Alpine Linux.
Technical Description
The vulnerability results from an interaction between OpenSSH's password verification mechanism and the crypt() function provided by musl libc.
When OpenSSH performs password authentication without PAM, it uses crypt() to process the submitted password and compare the resulting value against the account's stored password field.
Accounts that do not have a password configured may contain a single asterisk (*) in the password field. This normally prevents successful password authentication because the value is not a valid password hash.
However, musl libc returns * as an error indicator when the submitted password exceeds its supported length of 256 bytes.
Under the affected OpenSSH authentication conditions, this error value can be interpreted as a successful match against an account whose stored password field is also *.
Consequently, an attacker can potentially bypass password authentication by submitting a password between 257 and 1,024 bytes.
Attack Overview
The vulnerability can be understood through the following sequence:
Target Identification: An attacker identifies an SSH service running on an affected musl-based Linux system.
Configuration Requirements: The target must meet the vulnerable conditions, including OpenSSH operating without PAM, password authentication being enabled, and the presence of accounts with specific password-field configurations.
Long Password Submission: The attacker submits an unusually long password between 257 and 1,024 bytes.
Cryptographic Error Handling: musl libc's
crypt()function returns*as an error indicator because the password exceeds its supported length.Authentication Bypass: Under the vulnerable OpenSSH implementation, the returned value can match the stored
*password field of an account that has no password configured.Unauthorized Access: Authentication may succeed, allowing the attacker to access the affected account without knowing its actual password.
Note: This sequence describes the vulnerability's technical mechanism. It does not establish that a particular organization or server has been attacked.
Technical Analysis
1. Interaction Between OpenSSH and musl libc
OpenSSH relies on system libraries to perform several authentication-related operations.
In affected configurations, the SSH daemon uses musl libc's crypt() function to process submitted passwords.
The problem occurs when an unusually long password causes the library to return an error indicator that is identical to the stored value used by certain passwordless accounts.
This creates an unexpected authentication result.
2. Passwordless Account Handling
Linux systems can contain accounts that are intentionally configured without a password.
Their password field may contain *, which prevents normal password authentication.
Examples include:
Root accounts configured for key-based access.
Dedicated SSH key-only accounts.
Certain directory-service accounts.
The default
alpineaccount in affected official Alpine cloud images.
The vulnerability can make these accounts reachable through password authentication under the required conditions.
3. Affected Configurations
A system is vulnerable when the relevant conditions align:
It uses musl libc.
OpenSSH operates without PAM authentication.
SSH password authentication is enabled.
At least one account has
*in its password field.At least one other local account has a SHA-256 or SHA-512 password hash, commonly represented by
$5$or$6$.
The standard Alpine openssh-server package is affected under its default configuration.
The openssh-server-pam package with UsePAM yes is not affected by this specific issue.
4. Potential Privilege Escalation on Alpine Cloud Images
Alpine Linux also identified a specific risk involving its official tiny-cloud images.
Certain images include an alpine user with a * password field and passwordless doas privileges.
Under the vulnerable conditions, successful authentication as this account could allow an attacker to execute commands with root privileges through doas.
The affected image versions include older releases from Alpine 3.18.11 through 3.24.3. Images built from the fixed point releases are protected by the updated package.
This makes the issue particularly relevant to cloud-hosted Alpine instances and systems where administrators have added password-hash accounts.
Affected Products and Versions
| Component | Status |
|---|---|
Alpine standard openssh-server | Affected under specified conditions |
Alpine openssh-server-pam with UsePAM yes | Not affected |
| OpenSSH on musl without PAM | Affected under specified conditions |
| OpenSSH using glibc | Not affected by this specific issue |
| Dropbear SSH | Not affected by this specific issue |
Systems with PasswordAuthentication no | Not affected through password authentication |
The researcher also identified potentially affected musl-based environments beyond Alpine, including OpenWrt, Buildroot, and Yocto configurations. Actual exposure depends on the OpenSSH build and authentication settings.
Indicators of Compromise (IOCs)
No conventional malware indicators or malicious infrastructure were provided in the Alpine advisory.
However, Alpine Linux recommends investigating SSH authentication logs for suspicious successful password logins.
Important log indicators:
Unexpected
Accepted password forentries.Successful password authentication involving accounts that should only use SSH keys.
Unexpected logins for
root,alpine, or dedicated key-only users.Unusual
doasactivity following suspicious SSH authentication.Unexpected user creation, modified authorized keys, or unfamiliar files.
Suggested log location:
/var/log/messages
An Accepted password event for an account whose password field is * should be treated as a serious warning and investigated.
Potential Impact
Unauthorized Remote Access: Attackers who can reach an affected SSH service may gain access to accounts that are not intended to accept password-based authentication.
Privilege Escalation: On certain Alpine cloud images, access to the default alpine account may lead to root privileges through passwordless doas.
Server Compromise: Successful exploitation could expose sensitive files, application configurations, credentials, and system resources.
Cloud Infrastructure Risk: Vulnerable Alpine cloud images may expose virtual machines and workloads when the required account and authentication conditions are present.
Lateral Movement: If an affected server is compromised, attackers could potentially use its access and credentials to target additional systems within the environment.
Recommendations
Immediate Recommendations
Update OpenSSH: Upgrade to OpenSSH 10.6p2 or the corresponding fixed package provided by the Linux distribution.
Update Alpine Packages: Run
apk upgrade -U -ato obtain available security updates.Restart SSH: Restart the SSH daemon after upgrading because updating the package alone does not replace an already running process. Use
rc-service sshd restart.Disable Password Authentication: If patching is not immediately possible, set
PasswordAuthentication noin the SSH server configuration and restart the service.Review Authentication Logs: Examine
/var/log/messagesfor unexpected successful password logins involving passwordless or key-only accounts.Investigate Suspicious Access: Review
doasactivity, newly created accounts, modified authorized keys, and unexpected files on potentially exposed systems.
Preventive Recommendations
Enforce Key-Based Authentication: Prefer SSH public-key authentication and disable password authentication wherever operationally possible.
Apply Least Privilege: Avoid unnecessary privileged access and restrict administrative permissions.
Audit SSH Configurations: Regularly review
sshd_config, PAM settings, and account password-field configurations.Monitor Authentication Events: Configure alerts for unusual successful logins and unexpected access to administrative accounts.
Maintain Updated Base Images: Ensure cloud images, container environments, and Linux appliances receive security updates.
Review musl-Based Systems: Identify Alpine, OpenWrt, Buildroot, and Yocto systems that use vulnerable OpenSSH configurations.
Validate Security Fixes: Confirm that the running SSH daemon uses the patched version and that the expected authentication configuration is active.
Conclusion
The OpenSSH password authentication bypass demonstrates how seemingly small differences in error handling between software components can introduce serious security vulnerabilities.
By combining OpenSSH's password verification behavior with musl libc's handling of oversized passwords, the flaw could allow unauthorized access to accounts that were intended to remain inaccessible through password authentication.
The issue is especially important for Alpine Linux users because its standard OpenSSH package is affected under default authentication settings. OpenSSH 10.6p2 and Alpine's patched packages provide the necessary fixes.
Administrators should prioritize updates, review SSH authentication configurations, and investigate suspicious successful logins involving accounts that should never accept passwords.
