> status: mostly fine. patch anyway.practical AI security · est. 2026

Brief · Builders

sshhole: OpenSSH on Alpine Let Some Passwordless Accounts In. Update Today

By alkizz ·

First, the good news: a fresh Alpine image is not automatically open to root. According to the researcher, the dangerous path needs some other account on the box to have a real password set. Still, if you run sshd on Alpine or another musl Linux system, fix it today.

The fix is quick. Upgrade OpenSSH (upstream it's 10.6p2; on Alpine, apk upgrade openssh pulls your branch's fixed package), or set PasswordAuthentication no.

There's no CVE yet. I found no reported exploitation, and it's not in CISA's KEV catalog.

What went wrong

On Nov 5, OpenSSH shipped 10.6p2 with "a critical security workaround that affects Linux systems that use the musl libc and PAM disabled." It's a password authentication bypass. The researcher, Özgün Kültekin of Wakefield, calls it sshhole.

According to the researcher, musl's crypt() returns "" when it fails instead of an error, and some overlong passwords make it fail. For an account whose stored password field is just "", that failure looks like a match. The upstream fix is small: sshd now refuses to compare against any stored hash shorter than four characters.

OpenSSH says: "We consider the root cause of this bug to be outside sshd." Damien Miller of OpenSSH wrote that "we learned of the problem yesterday" and that they moved fast because of "rapid bug rediscovery by AI agents, sometimes within hours."

Who's actually exposed

Per the researcher, all of these have to be true:

Alpine's official cloud image build script creates an alpine user with a "*" password and gives it passwordless root through doas. That's why the cloud angle matters. But again, per the researcher, that account only becomes reachable once some other account on the box has a real password. The risky case is Alpine cloud VMs where someone has set a password on any account.

Plenty of things aren't affected. Per OpenSSH, glibc Linux, non-Linux systems, and PAM password auth are fine. Alpine's Natanael Copa checked dropbear and says it isn't affected. The official alpine Docker image has no sshd at all, so it only matters where someone added openssh. OpenWrt uses dropbear by default, so stock installs aren't affected; ones switched to OpenSSH could be.

If you run agent sandboxes or dev containers on Alpine and added openssh with password logins, you meet the conditions too.

Fixed versions

Alpine openssh-server, per Alpine's package index:

Alpine's Natanael Copa says all branches back to 3.16 are fixed. Upstream, the fix is OpenSSH 10.6p2.

What to do

Sources

← All briefs