⚠️ Critical OpenSSH (CVE-2026-123158) - password bypass

Sully (@Sully) Sully (@Sully)

⚠️ Urgent: Update OpenSSH on your Alpine Linux servers now (password bypass)

A critical flaw in OpenSSH lets an attacker log in to accounts that have no password, such as SSH key-only users, on many Alpine Linux servers. OpenSSH released a fix (10.6p2) on November 5, and Alpine has published patched packages for every release back to 3.16. No in-the-wild attacks have been reported yet, but the attack is simple and works reliably, so please don't wait.

Am I affected?

You're exposed if all of these are true:

  • You run Alpine's openssh-server package (built without PAM), or openssh-server-pam with UsePAM no
  • PasswordAuthentication is yes (the default)
  • Some account has no password set (* in /etc/shadow), e.g. key-only users, root on Alpine 3.16+, or the alpine user in official cloud images
  • At least one other account has a real password (a hash starting with $5$ or $6$)

Of special note: on tiny-cloud images from 3.18.11 to 3.24.3, the alpine user has passwordless doas. If anyone has set a password on any account (even just for console access), an attacker can log in as alpine and become root.

You're not affected if sshd isn't running, if PasswordAuthentication no is set (cloud-init images set this), or on glibc-based distros and PAM-based setups.

How to fix it

Upgrading does not restart the running sshd, so do both steps:

apk upgrade -U openssh
rc-service sshd restart

Alpine point releases 3.21.10, 3.22.8, 3.23.8 and 3.24.4 already include the fix.

Can't update right away? Disable password logins

  1. Confirm your SSH key login works, and keep your current session open.
  2. Set PasswordAuthentication no, including in any Match blocks in /etc/ssh/sshd_config and in files under /etc/ssh/sshd_config.d/.
  3. Check the config with sshd -t, then rc-service sshd restart.
  4. Verify: sshd -T | grep -i passwordauthentication should print passwordauthentication no.
  5. Test a fresh login before closing your old session.

Check whether you were hit

Search /var/log/messages for Accepted password for lines naming an account that has no password (alpine, root, or a key-only user). On exposed machines, also review doas usage, recently created users, and authorized_keys files. If you can't rule out an unauthorized login, treat the server as compromised.

grep -h "Accepted password" /var/log/messages*
grep -h "doas" /var/log/messages*

More info

  • Alpine security advisory: https://alpinelinux.org/posts/2026-11-05-openssh-password-authentication-bypass/
  • OpenSSH 10.6p2 release notes: https://www.openssh.org/releasenotes.html#10.6p2

Please reply here if you run into trouble updating.

Replies (0)

No replies yet.

Log in to reply.