OpenSSH 10.6p2 closes a password bypass that only hits musl systems such as Alpine
CVE-2026-123158 lets logins through on accounts with no password when sshd runs on musl without PAM. A checklist for who is exposed, and what to do before patching.
- Section
- Security & Privacy
- Published
- Read
- 4 min
- Sources
- 3
Most OpenSSH servers are not affected by CVE-2026-123158, and that is exactly why it is easy to get wrong. The bug lets someone log in over SSH to an account that has no password at all, but only on a narrow slice of Linux: sshd built without PAM and running on the musl C library. Alpine Linux is the best-known example. The OpenSSH project shipped a workaround in 10.6p2 on November 5, and by November 9 CISA had put the flaw on its Known Exploited Vulnerabilities list, according to eSecurity Planet.
Are you exposed? Work through this
According to OX Security’s analysis, all of the following must be true:
- OpenSSH is older than 10.6p2.
- sshd runs on musl libc with PAM disabled. OX names Alpine, OpenWrt, Buildroot and Yocto builds as examples.
- Password logins are enabled.
- At least one account has no valid password, marked with
*in/etc/shadow, and at least one other account has a real one.
You are not affected, OX says, on glibc-based distributions, on PAM-based setups, with PasswordAuthentication no, on Dropbear, or on OpenBSD’s SSH. That list matters, because the Alpine base images behind a great many containers match every condition by default. OX points out that on Alpine’s official AWS and Azure images the default alpine user can use passwordless doas, so a successful bypass can lead straight to root.
What the bug is
No cryptography is broken and no memory is corrupted. OX describes three long-standing behaviors that combine badly. musl’s crypt() returns the string * when the password it is given is longer than 256 bytes. Linux uses * in the shadow file to mean “this account has no valid password.” sshd then compares the two values, finds them equal, and accepts the login.
The OpenSSH notes say the release “contains a critical security workaround” for this case. They also make a point of assigning blame: “We consider the root cause of this bug to be outside sshd, but it is exploitable via sshd and can be avoided there.” So the fix lives in OpenSSH even though, in the project’s view, the cause does not. The bug was reported by Özgün Kültekin of Wakefield. OX dates the underlying issue to 2016 and says Alpine’s 3.16 default account setup in 2022 supplied the last condition, which makes it, in OX’s words, a decade-old bug.
How serious is it, and is it being exploited?
OX rates it CVSS v3.1 8.1, High, and says it found no confirmed in-the-wild exploitation at the time of writing. eSecurity Planet reports the opposite end of the timeline: the CISA listing confirms active exploitation, and attribution and victim counts are unknown. I read both, and they do not contradict each other so much as date from different days. The safe assumption is the later one. CISA’s deadline for federal agencies was November 12, and the agency’s list is the stronger signal.
The same CISA batch included GPUStack, FreeSWITCH and IBM Aspera Faspex flaws. Only the OpenSSH entry depends on a quirk of the C library, which is why it needs a checklist rather than a blanket “patch now.”
What to do
- Patch. Upgrade to 10.6p2; on Alpine, OX gives
apk upgrade -U -a. Then restart sshd, because the running daemon keeps the old code. Rebuild container and cloud images from a fixed base. - If you cannot patch today, confirm that key-based login works first, then disable password authentication.
- Look back. Check logs for successful password logins on accounts that have no password.
- Do not run public proof-of-concept scripts or “checker” tools you have not read. OX warns specifically against this, and it is good advice for any exploited bug.
The lesson here is smaller than the headline. A password-authentication bypass sounds universal, but this one was a seam between two components, and only people who knew which C library their servers used could tell right away whether they were in danger. If you cannot answer that question for your fleet, that gap is the more urgent finding.
Sources
More in Security & Privacy
-
BeyondTrust's exploited zero-day: why patching a self-hosted appliance is only the first step
CVE-2026-102764 was used against Remote Support from late August, weeks before the October 15 advisory. What the patch fixes, and what it does not clean up.
-
Iris Ohyama's 7.7 million figure is a ceiling, and four basic facts of the breach are still unknown
The Japanese homeware maker's online store has been offline since October 28. What the company has confirmed about the cloud breach, and what it has not said.
-
Wyndham's Android app shipped with a database password inside it, the second such find in two weeks
A researcher found a hardcoded credential in Wyndham's app that opened a Salesforce-hosted database. Wyndham revoked it but won't say whether logs can show earlier access.