CVE-2026-123158 – OpenSSH login bypass

Password bypass in sshd on musl Linux without PAM – CVSS 3.1: 8.1 (High)
November 6, 2026 · CVE-2026-123158 · OpenSSH · musl · Security · Homelab
Fix available — As of November 6, 2026: OpenSSH closed the flaw with version 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.
Blue 3D symbolic illustration with a server, an open padlock and a key. CVE-2026-123158: OpenSSH login bypass on musl Linux without PAM; CVSS 3.1 by Red Hat: 8.1, high.
AI-generated symbolic illustration for CVE-2026-123158. Certain OpenSSH configurations on musl Linux without PAM are affected. CVSS 3.1: 8.1 per Red Hat; as of November 6, 2026.

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.

Technical core: For an account whose password field contains no valid hash format, the password check misinterprets the input. The result: any password between 256 and 1024 characters is accepted. The root cause is the interaction between OpenSSH's password verification and musl libc's 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.

Scope: Systems using glibc (Debian, Ubuntu, Fedora, RHEL …) and all installations with PAM are not affected. Red Hat also classifies its own products as unaffected. The risk is concentrated on musl-based systems without PAM.

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
Homelab note: Alpine as a base image for containers (e.g. mail server images) is not a problem on its own — what matters is whether a 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
Effect: After the restart, nobody can log in with a password anymore — keys only. This stops the bypass and is a security improvement worth keeping in the long run.

Sources