Portable OpenSSH 10.6p2 landed on Nov. 5, 2026 with a critical security workaround for a password authentication bypass on some Linux systems. The OpenSSH vulnerability patch is small. The operator work is larger: figuring out whether your fleet even runs the risky stack, and what “password-disabled” means in /etc/shadow versus turning password logins off in sshd. A reproducible bypass is not evidence of a verified exploitation wave; the primary sources cited here do not establish a within-hours attack timeline. What they do establish is a sharp, reproducible login path on musl hosts without PAM—and a same-day response plan you can actually run.
How This OpenSSH Vulnerability Is Exploited—And What to Patch
Start with the vendor note. The OpenSSH 10.6p2 release notes say the release contains a critical security workaround that affects Linux systems that use musl libc with PAM disabled. Damien Miller’s project text is careful: the team considers the root cause outside sshd, but the condition is exploitable through sshd and can be avoided there. The bug was reported by Özgün Kültekin of Wakefield. Fixed portable builds are labeled 10.6p2; Alpine published its advisory the same day.
CVE-2026-123158, published Nov. 5, 2026, describes sshd in OpenSSH before 10.6p2 on Linux when musl libc is used without PAM: for some account configurations, an oversized password succeeds. Alpine Linux is named as an example platform. That is not a blanket claim that every OpenSSH daemon on the internet is open. Glibc hosts, OpenBSD, Dropbear, and sshd builds that actually use PAM for password checks sit outside this bypass path.
The mechanism, as documented on the researcher’s *sshole site and restated in Alpine’s advisory, is an interaction—not classic key authentication “working as designed.” Accounts with * in the shadow password field are supposed to reject every password. Musl’s crypt() can return the string * as an error when a submitted password exceeds its length limit. In the non-PAM path, OpenSSH may borrow a real salt from another account that has a $5$ or $6$ hash so timing does not leak usernames. Hash the oversized password with that salt, get * back, compare it to the target account’s stored *, and the comparison can succeed. Researcher and Alpine guidance put the practical password length window at 257 to 1,024 bytes. Key-based logins are not the bug; confusing a crypt error token with a disabled-account marker is.
Password-Disabled Is Not PasswordAuthentication No
Three different account and config states keep getting mashed together in chat threads. Keep them separate on the ticket.
- Password-disabled (* in shadow): No usable password hash. Common for key-only users and some service accounts. This is the account state the bypass targets when the rest of the stack lines up. Other login restrictions still apply: Alpine notes that the default PermitRootLogin prohibit-password protects root from this password path; an accessible account with passwordless doas can still provide a route to root.
- PasswordAuthentication no: An sshd setting that refuses password logins entirely. Alpine and the researcher both list it as the immediate mitigation if you cannot patch yet. It is the opposite of “password auth still on,” which is a prerequisite for this path.
- Locked with !: Alpine’s advisory says accounts whose password field is ! are not susceptible through this * comparison. Historically Alpine also learned that locking with ! can break key logins when PAM is off—which is why some images moved to * and walked into this interaction later. Do not “fix” a fleet by flipping every * to ! without understanding key login side effects.
Alpine’s Nov. 5, 2026 security advisory is blunt: if you run sshd on Alpine, update openssh and restart sshd; upgrading the package alone does not replace the running daemon. You are in scope when you run the non-PAM openssh-server package (or openssh-server-pam with UsePAM no), PasswordAuthentication is still yes, and an account with a * password field exists alongside at least one account with a usable $5$/$6$ hash. Official cloud images with a default alpine user and passwordless doas raise the stakes after a console password appears elsewhere on the box. Alpine noted that no CVE identifier had been assigned at the time of writing; CVE-2026-123158 carries the same publication date. Prefer the fixed package matrix Alpine published for your release branch over guessing from portable tarball names alone.
A Same-Day Response Plan for Your SSH Fleet
The following is my analysis as an operator. Treat the timed drill as hypothetical unless your change board already authorized an emergency window.
- Inventory the stack, not just the banner. Ask which hosts run musl (Alpine, OpenWrt, Buildroot, Yocto appliances, some containers that expose sshd) and whether PAM is actually in the password path. A glibc Ubuntu bastion with UsePAM yes is a different work item than an Alpine edge node.
- Patch or mitigate in that order. Move affected builds to OpenSSH 10.6p2 or the distro’s fixed package, then restart sshd. If the package lag is real, set PasswordAuthentication no, validate with sshd -t, restart sshd, and verify with sshd -T. Check applicable Match blocks too, using connection-specific sshd -T -C parameters where needed. Keep an existing session and a recovery path available, then test a new authorized connection before closing the change. That mitigation is temporary discipline, not a substitute for the upstream workaround on hosts you intend to leave reachable.
- Hunt logs for impossible password successes. The researcher points operators at authentication logs where an account that should never accept a password shows a successful password login. Correlate with shadow: if the field is still *, treat that as a compromise indicator and rotate keys, tokens, and anything that account could reach. Do not invent a global breach rate from a lab reproduction.
- Hypothetical same-day drill: Within one change window, list every internet-reachable SSH listener you own, flag musl/non-PAM candidates, push the fixed package or the password-auth kill switch, restart sshd, and sample logs for password accepts on * accounts. That is a tabletop you can schedule—not evidence that honeypots were rooted hours after disclosure.
What we know from primary notes: Nov. 5, 2026 brought OpenSSH 10.6p2, Alpine packages, CVE-2026-123158, and a clear musl-without-PAM exploit path against password-disabled (*) accounts while password authentication remains enabled. What we do not know from those same sources is a verified “within hours” mass exploitation wave. Patch the hosts that match the prerequisites. Keep the vocabulary honest so the next person on call does not “mitigate” the wrong setting.
