SSHole: One 257-Byte Password Logs Into Password-Disabled Alpine Linux Servers — and Attackers Found Them Within Hours

SSHole: One 257-Byte Password Logs Into Password-Disabled Alpine Linux Servers — and Attackers Found Them Within Hours

SSHole: One 257-Byte Password Logs Into Password-Disabled Alpine Linux Servers — and Attackers Found Them Within Hours

A flaw that has existed in OpenSSH's password handling for a decade became this week's fastest-moving Linux story. On November 5, security researcher Ozgun Kultekin of Wakefield disclosed CVE-2026-123158 (CVSS 8.1), nicknamed SSHole or "*sshole," and OpenSSH shipped an emergency 10.6p2 release the same day. The bug lets an unauthenticated attacker log in to accounts that deliberately have no password set at all — by sending one oversized password. It affects OpenSSH running on the musl C library with PAM disabled, which is Alpine Linux's default OpenSSH server configuration, plus other musl-based systems such as OpenWrt, Buildroot, and Yocto.

The mechanics are almost comically simple, which is what makes them dangerous. An account whose password field in /etc/shadow is * — the normal state for key-only accounts, and for root in Alpine base images since 3.16 — cannot normally log in with a password. But when the attacker sends a password between 257 and 1,024 bytes on a system that also has at least one account with a $5$ or $6$ password hash, the hash computation fails and returns the same asterisk value. sshd then compares the attacker's failed result against the stored * — and the login succeeds. One connection, works every time, no retries needed. The behavior traces back to a 2016 patch for CVE-2016-6210, and Kultekin says he found the bug after running roughly 17,600 authentication tests with AI agents across different OpenSSH configurations, malformed hashes, and oversized passwords.

The not-affected list is as important as the affected one: glibc-based distributions, Dropbear, systems that check passwords through PAM (Alpine's openssh-server-pam with UsePAM yes), configurations with PasswordAuthentication no, locked accounts (! fields), cloud-init provisioned images, and containers that don't run sshd are all safe. That still leaves a huge population of Alpine servers, embedded appliances, and edge boxes where one key-only account plus one password-holding user is a completely normal setup.

Exploitation did not wait for the weekend. Threat intelligence firm Previdian observed the first exploitation attempt less than nine hours after the CVE publication, and confirmed successful root access on a honeypot running Alpine Linux and OpenSSH. Eight attempts came from one IP address geolocated to Japan (89.116.89[.]18), using oversized passwords to bypass authentication and then running reconnaissance commands — id, uname, hostname — through non-interactive SSH sessions. "A successful SSHole attack grants access with the compromised account's existing permissions," Safe Security noted, pointing to deployment credentials, application secrets, and lateral movement as the follow-on risk. The flaw is not yet in CISA's KEV catalog.

Fixes are already everywhere: OpenSSH 10.6p2 refuses a match when the stored password field is shorter than four characters, and Alpine has pushed patched packages for every supported branch — the 3.21.10, 3.22.8, 3.23.8, and 3.24.4 releases all carry the fix, with backports down to 3.16. One critical detail from Alpine's advisory: upgrading the package alone does not replace the running daemon — you must restart sshd.

What Should You Do?

  1. Update and restart. Install OpenSSH 10.6p2 or your distribution's patched package (on Alpine, apk upgrade -U -a), then restart sshd — the running daemon must be replaced, not just the files on disk.
  2. Can't update yet? Close the hole anyway. Set PasswordAuthentication no in sshd_config and restart. Either action closes the vulnerability.
  3. Hunt for signs of abuse. Search /var/log/messages for lines reading "Accepted password for" on accounts that should never accept passwords — root, key-only users, service accounts. Review recent doas usage, newly created users, files, and authorized keys on exposed machines.
  4. Treat unexplained logins as compromise. In Alpine's words: "If you cannot rule out a login, treat the machine as compromised" — rotate credentials, keys, and anything the account could reach.

The WAF Angle

SSH never crosses a WAF, so the web tier won't see this attack — but SSHole is a textbook authentication-logic failure, the same species as the signature-evading bugs we block at HTTP: input that is technically "valid" (a password, just a long one) that exploits a comparison edge case and returns a legitimate-looking success. The detection lesson transfers directly. The single highest-signal artifact of this attack — a successful password login for an account that has no password — is invisible to signature matching and trivially obvious to anomaly logic, whether that runs in your WAF's behavioral scoring or your SSH log monitoring. And the affected population is exactly the long tail our industry forgets: musl-powered appliances, containers, and edge devices that nobody patches because "they're small." That is the same blind spot that let a GitLab CI flaw nearly own Alpine's whole package pipeline during the Alpine Linux rebuild last week, and the same unmanaged-SSH blast radius that made Tailworm's Tailscale flaws so dangerous in October.

Sources