CVE-2026-123158
🔴 High In CISA KEVOpenSSH sshd, but only on musl libc without PAM, which in practice means Alpine Linux and Alpine-based container images. The openssh-server package is affected, and openssh-server-pam is affected only when UsePAM no is set. CERT Santé's alert of 06/11/2026 widens this materially: besides Alpine it names OpenWrt, Buildroot and Yocto builds of sshd built without PAM, and Alpine tiny-cloud images 3.18.11 to 3.24.3, where the default alpine user has passwordless doas. Dropbear is not affected. An estate that checked only its Alpine hosts has not finished · OpenSSH before 10.6p2. Alpine ships fixes back through its stable branches: 10.6_p2-r0 (edge), 10.3_p1-r2 (3.24), 10.2_p1-r1 (3.23), 10.0_p1-r11 (3.22), 9.9_p2-r1 (3.21), 9.7_p1-r6 (3.20), 9.6_p1-r3 (3.19), 9.3_p2-r4 (3.18), 9.1_p1-r7 (3.17), 9.0_p1-r6 (3.16)
97.35th percentile
due 2026-11-12
Exploitation
PasswordAuthentication yes, plus an account whose password field is * (which is root in the Alpine base image, and also key-only and directory-service users with no shadow entry), plus at least one other local account with a $5$ or $6$ hash. Alpine's own advisory states the consequence plainly: an attacker who can reach the SSH port logs in without a password in a single connection, reliably and without retries, and one account with a password hash makes every account without one reachable. The CVE record's framing, that any password of 256 to 1024 characters is accepted, is the same bug seen from the other side. AC:H understates this Rechecked on 09/11/2026: CERT Santé independently confirms the proof of concept, stating that one is available in open sources, and states the flaw is not actively exploited. That corroborates the PoC mark on this row from a second source. It also now has an EPSS score, 1.014%, which it lacked when the row was written. Rating unchanged at 🟠 Updated 10/11/2026, and this row is now 🔴. CISA added it to KEV on 09/11/2026 and the record's SSVC reads exploitation active, automatable no, technical impact total. One day old at this run, so comfortably inside the 60-day window. The promotion rests on CISA, not on the supplied list, which for this id turned out to be Sploitus-sourced and therefore evidence of a published exploit rather than of exploitation. A caution on how that SSVC changed: its timestamp still reads 05/11/2026 and its value on 06/11 was poc, so CISA flipped the option from poc to active without moving the timestamp — the documented ADP behaviour in which only providerMetadata.dateUpdated (now 10/11/2026 04:55 UTC) is a reliable change signal. Reading the SSVC timestamp alone would have missed this.Timeline
- 05/11/2026CVE record published (CVE List)
- 09/11/2026OpenSSH "SSHole" auth bypass
- 09/11/2026Added to the CISA KEV catalogue
- 11/11/2026CISA KEV: OpenSSH "SSHole" + three critical pre-auth flaws
- 12/11/2026CISA deadline for US federal agencies
Relationships
exploits suspected named in the same story vendor · Select a box to open its page · All relationships
Risk
crypt() returns * as an error indicator for keys over 256 bytes, and sshd treats that return as a password hash)Fix
sshd must be restarted, and the workaround is PasswordAuthentication no followed by the same restart. Alpine also advises reviewing /var/log/messages for suspicious password logins and treating the host as compromised if such a login cannot be ruled out. CERT Santé adds a second workaround the Alpine advisory does not: use the openssh-server-pam package with UsePAM yes, which is not affected. It also gives the concrete sequence apk upgrade -U -a followed by rc-service sshd restart, warns to set PasswordAuthentication no inside Match blocks too, to validate with sshd -t, and to confirm key-based login works and keep an existing session open before restarting. Where neither the upgrade nor the workaround can be applied, it says to disable SSHOfficial description
sshd in OpenSSH before 10.6p2 on Linux, when musl libc is used without PAM, lacks a workaround for a password authentication bypass (related to misinterpretation of whether a string is intended to be a password hash). For some configurations of accounts, any password between 256 and 1024 characters succeeds. An example of a platform using musl libc without PAM is Alpine Linux.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
CWE-394