OpenSSH *sshole, CVE-2026-123158, Opens Password-Less Accounts on musl Servers
Security / news
OpenSSH *sshole, CVE-2026-123158, Opens Password-Less Accounts on musl Servers
The bypass needs five conditions at once, and sources disagree on whether it is being exploited; the fix needs an sshd restart.
An unauthenticated remote attacker can log in over SSH to any account whose password field is * by submitting a password of 257 to 1,024 bytes, provided the server runs OpenSSH on musl libc without PAM and another account holds a real password hash. OpenSSH 10.6p2, released Nov. 5, 2026, contains the fix for the flaw, tracked as CVE-2026-123158 and nicknamed *sshole.
Updating the package is not enough. The running sshd process keeps the old code until it restarts, according to the Ox Security write-up. On Alpine, the sequence is apk upgrade -U -a followed by rc-service sshd restart.
Five conditions, all required
Ox Security lists the preconditions. The server runs on musl (Alpine, OpenWrt, Buildroot or Yocto). It does not use PAM, which is Alpine's default for the openssh-server package. Password logins are enabled, which is the OpenSSH default. At least one account has * as its password. At least one other account has a real hash.
glibc systems such as Debian, Ubuntu and Fedora are not affected. Neither are servers using PAM, servers with PasswordAuthentication no, accounts locked with ! instead of *, Dropbear or OpenBSD's SSH.
The cause is three decisions that were each defensible alone, per Ox. musl's crypt() returns * when it refuses a password over 256 bytes. OpenSSH, since a 2016 change made as part of its CVE-2016-6210 fix, can hash a password using another account's salt when the target has no valid hash. Alpine, since 3.16 in 2022, writes * into the root and key-only accounts' password fields. The two * values then compare equal. Ox says the flaw is "not a cryptographic weakness or a memory-corruption vulnerability."

BleepingComputer reported on Nov. 5 that the researcher, Özgün Kültekin of Wakefield, said AI agents ran about 17,600 authentication tests across OpenSSH configurations, malformed hashes and oversized passwords. The same article names OpenWrt, Buildroot and Yocto builds as possibly affected under certain configurations. The OpenSSH release notes credit Kültekin and call the release a "critical security workaround", saying the root cause lies outside sshd.
How bad it is on Alpine
On Alpine's official AWS and Azure images, the default alpine user has passwordless doas. Ox says that a successful login to it "can allow an attacker to escalate to root." Cloudflare's Radar page adds a condition: on the tiny-cloud images (3.18.11 through 3.24.3), that user only becomes reachable once a $5$ or $6$ hash exists on the box, for example after an admin sets a console password. Root is reachable only if PermitRootLogin is yes.
The score of 8.1 (CVSS 3.1, High) understates the position on any image that matches all five conditions, because the attack needs one request and no credentials. It overstates the position for the large majority of Linux servers, which use glibc or PAM.
Exploitation: two accounts that do not agree
Whether anyone is using it is disputed. eSecurity Planet reports that CISA added CVE-2026-123158 to its Known Exploited Vulnerabilities catalog on Nov. 9, with a Nov. 12 deadline for federal civilian agencies. The listing rests on that account, because the CISA catalog was not checked directly. Ox and Cloudflare, whose pages date from Nov. 5 and 6, do not report exploitation. Cloudflare's page says "Neither OpenSSH nor Alpine had reported exploitation as of November 6," and notes that CISA's assessment lists a public proof of concept but does not consider the attack automatable.
The same Nov. 9 batch included two flaws already covered here: the GPUStack admin bypass and the FreeSWITCH SIP MESSAGE injection.
| Alpine branch | Fixed openssh package |
|---|---|
| edge | 10.6_p2-r0 |
| 3.24 | 10.3_p1-r2 |
| 3.22 | 10.0_p1-r11 |
| 3.20 | 9.7_p1-r6 |
| 3.16 | 9.0_p1-r6 |
Alpine pushed fixes back to 3.16, including branches it no longer supports. Branches 3.23, 3.21, 3.19, 3.18 and 3.17 also have fixed packages, per Ox.
What to do
Patch, then restart sshd. If a patch is not possible yet, confirm key login works, set PasswordAuthentication no and restart. Rebuild Docker and cloud images from a fixed base. Search logs for "Accepted password for" entries on accounts that should have no password, and treat any hit as a compromise. OpenSSH's notes give no further workaround, and neither Ox nor Cloudflare reported an affected-host count.
Sources
More in Security
- 01Java4Shell Scores 9.2 From Its Finder and 8.1 From OpenJDK, and Needs an AVX-512 CPUCalif says a 65-character Base64 string overwrites 62 bytes of Java heap and reaches code execution in Keycloak, Jenkins and Jira. A second security firm says the source shows only a crash.
- 02CISA Gave 9 of 16 November KEV Entries a Three-Day Deadline With Forensic Triage, and 7 Got 14 DaysThe catalog's own due-date and forensicTriage fields show two tiers under BOD 26-04. Sorting November's additions by tier shows which exploited bugs CISA treats as already-compromised-until-proven-otherwise.
- 03Project Zero Cuts Its Disclosure Deadline to 60 Days on Feb. 2, 2027, Then 30 in 2028Google's bug-hunting team is dropping the 30-day patch soak period and counting every deadline from the day it reports, citing AI-assisted exploitation.
- 04Google Finds exploit_agent Diffing Patches and Firing Exploits With No Operator in the LoopGTIG's November 16 tracker reports the first fully automated discovery-to-exploit pipeline it has seen, found on an exposed staging server, plus 22 zero-days in August.