Alpine and musl flaw: passwordless SSH login under certain configurations
A decade-old vulnerability allows passwordless SSH access to Alpine Linux machines with musl and OpenSSH without PAM. We analyze the real risk for SMBs and what to check.
4 min read

In this article
A silent flaw that has been there for a decade
There are vulnerabilities that frighten because of how spectacular they are and others that do so because of how discreet they are. The one we are dealing with belongs to the second group: it affects machines running certain configurations of Alpine Linux —and possibly other distributions— and allows an attacker to log in via SSH without needing a password. The origin lies in the interaction between OpenSSH and musl, the lightweight library that replaces libc in Alpine, and it has been present for around a decade.
It is worth stressing from the outset that this is not a universal flaw in Linux or in OpenSSH in general. It is the specific combination of pieces that opens the door. And as usually happens in security, the devil is in the configuration details.
The three conditions that must occur at the same time
For exploitation to work, according to the published information, several elements must coincide. It is not enough to have Alpine: very specific circumstances must be chained together.
- OpenSSH on musl without PAM. The OpenSSH binary must be compiled against musl and must not use PAM, the framework that manages authentication and access checks for accounts.
- An account with a password hashed in SHA256 or SHA512. The system must have at least one account accessible through a password stored with those hash functions.
- An account configured as “passwordless.” In /etc/shadow, the password field for that account must contain an asterisk (“*”). This is a common pattern in accounts that authenticate via certificates.
When those pieces fit together, the attacker manages to log in with a single connection, without retries and without credentials. That “it works on the first try” is precisely what makes the flaw dangerous: there is no brute force, no noise, no window of failed attempts that raises suspicion.
Why Alpine matters more than it seems
Alpine is not an exotic distribution. Its lightness has made it a very popular option for containers, appliances, routers, IoT devices and virtualized environments where every megabyte counts. Many SMBs have it in their infrastructure without knowing it, embedded in Docker images or in network equipment managed by external providers.
The use of musl instead of glibc is a design decision that brings advantages in size and simplicity, but it also creates corners less traveled by the security community. Flaws that depend on the interaction between libraries and services are especially elusive: they do not appear in superficial tests and can remain latent for years, as is the case here.
What it means for an SMB or an IT team
The good news is that exploitation requires a very specific configuration. The bad news is that this configuration is not rare in environments where certificate-based authentication and service accounts are mixed. If your team manages Alpine servers, containers based on it, or devices that expose SSH, it is worth reviewing carefully.
The real risk is not so much the initial access as what comes afterward: an attacker inside the system can pivot to other services, read secrets, modify configurations or deploy persistence. In an SMB with limited resources, an incident like this can paralyze operations for days.
Practical recommendations
- Take inventory before acting. Locate which machines run Alpine or derivatives with OpenSSH on musl and without PAM. If you do not know, you cannot protect it.
- Review the accounts with “*” in /etc/shadow. Identify which ones they are and whether they really need to be exposed via SSH.
- Limit the SSH surface. Restrict access by IP, use bastions, disable direct login where it is not essential and apply the principle of least privilege.
- Follow the project's updates. Since this is a flaw in the interaction between components, the patch may come through either path. Keep OpenSSH and musl up to date and verify official advisories.
- Monitor anomalous logins. A successful passwordless access leaves a trace in the logs. If you do not review them, you will not see it.
This case is reminiscent of other recent advisories we have discussed on the blog, such as the one on SHA pinning or the one on the Anthropic extension in Cursor: security does not depend on a single piece, but on how they all fit together. A seemingly secondary component can become the entry point.
Our reading from ForgeNEX
This is not an alarm to run around in circles, but it is a useful reminder: configurations matter as much as versions. Many SMBs believe they are protected because they update, but the flaw lives in the combination of settings. Reviewing the authentication architecture, documenting which accounts exist and why, and limiting who can talk to SSH are measures that cost little and prevent bigger scares.
If your team is not clear about what is running in your infrastructure, that is the first problem to solve. Visibility is the basis of any sensible security strategy.
Source: Ars Technica. Analysis and adaptation: ForgeNEX.
Keep reading
- WordPress 7.1.5 fixes 20 flaws: unauthenticated RCE and critical SQL19 November 2026
- SHA pinning is no longer enough: the warning every SME should read18 November 2026
- Cyberattack on the cold chain: the real risk for SMEs and supermarkets17 November 2026
- N-able fixes 17 critical flaws in N-central and warns of crypto miners17 November 2026
- Mior and Skyfall break trust in AMD SEV-SNP16 November 2026