CVE-2026-123158 – OpenSSH login bypass
10.6p2 (November 5, 2026). Alpine Linux ships patched openssh packages for all supported branches (3.16–3.24, edge) — one update is enough. Until then, PasswordAuthentication no closes the attack path completely.
On November 5, 2026, the OpenSSH project closed a flaw in its password checking with version 10.6p2: on musl libc without PAM, an attacker can bypass authentication for certain account configurations with a long password. On affected systems — first and foremost Alpine Linux — the bug is publicly reproducible and exploitable without knowing the real password.
This short post explains who is affected, why typical desktop and server systems usually are not, and what to do.
crypt() error handling (CWE-394: Unexpected Status Code or Return Value).
What happened?
The vulnerability affects sshd in OpenSSH before 10.6p2 when it is linked against musl libc and runs without PAM. That is the default configuration of the openssh-server package on Alpine Linux — similarly configured systems such as OpenWrt, Buildroot or Yocto are affected as well.
- Impact: authentication as an account whose password is locked or lacks a valid hash — any arbitrary password of 256–1024 characters is enough. On Alpine cloud images with passwordless
doas, that is sufficient for root. - Requirements: the attacker must reach port 22. The default
rootlogin remains protected byPermitRootLogin prohibit-password. - Rating: CVSS 3.1 8.1 (High) per Red Hat; NVD analysis is still pending.
Am I affected?
For a typical Linux desktop and the common server distributions, the answer is no — there, authentication is implemented via PAM and glibc. It is worth checking everything based on Alpine or running sshd in a container or appliance:
| System | Affected? | Reason |
|---|---|---|
| Debian / Ubuntu / Fedora / RHEL (desktop & server) | No | glibc + PAM |
Alpine Linux with openssh-server |
Yes | musl, default without PAM |
| Alpine-based containers with a running sshd | Yes | musl, if sshd actually runs |
| OpenWrt routers, musl/ash appliances (Buildroot, Yocto) | Yes | musl, usually without PAM |
sshd actually runs and is reachable inside the container. If not, the flaw does not apply.
Fix & mitigation
OpenSSH fixed the flaw in 10.6p2 (November 5, 2026). Alpine Linux has published adapted packages for all supported branches from 3.16 to 3.24 and edge — updating the package is sufficient.
# Alpine – update openssh apk update && apk upgrade openssh # Immediate mitigation if no update is possible: nano /etc/ssh/sshd_config
Until a patch is installed, this configuration completely closes the attack path:
# Set in sshd_config PasswordAuthentication no ChallengeResponseAuthentication no # Restart the service rc-service sshd restart # Alpine systemctl restart sshd # systemd