CYBERVERTEX

OpenSSH emergency release closes password bypass on certain Alpine Linux servers

OpenSSH 10.6p2 addresses a critical authentication bypass affecting particular musl-based Linux configurations without PAM. Administrators need to check exposure and restart updated SSH services.

What happened

The OpenSSH project released portable version 10.6p2 on November 5 with a critical security workaround for an authentication bypass affecting some Linux systems built with musl libc and running without PAM. The project's dated release notes confirm that the issue is exploitable through sshd, while noting that it considers the underlying cause to lie outside sshd itself. The Hacker News independently reported that certain Alpine Linux servers can accept an overlong password for an account that was intended to have no password login. Exposure depends on several configuration conditions: password authentication must be enabled, PAM must not be handling authentication, a target account must have a particular password-disabled marker, and another account must have a suitable password hash. This is not a universal OpenSSH flaw affecting every Linux server. Alpine published updated packages, and the upstream release provides a workaround for systems built directly from OpenSSH source.

Why it matters

SSH is a common administrative entry point for servers, embedded systems and network appliances. A mistaken assumption that a key-only account cannot be reached through password authentication can create an unexpected remote-access risk. Alpine Linux is a prominent example because its standard OpenSSH server package is built without PAM, but other musl-based deployments deserve configuration-specific review. Systems using glibc or PAM-based authentication are not affected by this particular issue, according to the OpenSSH team. The difference matters: indiscriminate warnings can waste remediation time, while overlooking a small set of exposed systems can leave privileged administrative access at risk. Reports available at the time of the release did not establish active exploitation in the wild. The urgency comes from the severity of the possible bypass and the availability of a fix, not from a verified widespread attack campaign.

What to watch next

Operators should identify whether they run sshd on musl-based Linux without PAM, review password-authentication settings, and apply their distribution's corrected OpenSSH package. On Alpine, The Hacker News notes that a package upgrade should be followed by restarting the running sshd service; merely installing a new binary does not replace an already running daemon. Where a patch cannot be applied promptly, administrators can evaluate disabling SSH password authentication after verifying that an alternate administrative login works. Teams maintaining appliances or custom images should ask vendors whether their builds use the affected combination and when corrected images will ship. Future advisories may clarify identifiers, affected versions and any evidence of exploitation. A configuration audit is more reliable than assuming that every installation of OpenSSH is either vulnerable or safe.

Reality check. The issue requires a specific combination of musl, non-PAM sshd, password authentication and account state. The OpenSSH release confirms the workaround; independent reporting supplies the detailed Alpine conditions. No confirmed exploitation campaign was established in the reviewed sources.
Sources and further reading

← Back to archive