GPU VulnDB

Database/Kernel, userspace & hypervisor

OpenSSH sshd: password authentication bypass on musl libc builds without PAM

CVSS 8.1CVE-2026-123158Kernel, userspace & hypervisorcurated

Impact

On systems where sshd is linked against musl libc and built without PAM, some account configurations accept any password between 256 and 1024 characters, giving an unauthenticated remote attacker interactive shell access as that account. Alpine Linux is the named example platform, which matters because Alpine is a common base for container images and for utility/jump hosts in a datacenter. Any Alpine-based bastion, management container or sidecar that exposes sshd with password authentication enabled is directly reachable login-bypass exposure, and from a management-network bastion that is the shortest path into the GPU fleet.

Who can reach it

Anyone who can reach port 22 on an affected host. No authentication and no valid credential needed - only a username whose password hash field is in the affected form. Only applies to sshd on musl libc builds with PAM not in use.

What to do

Upgrade to OpenSSH 10.6p2 or later (the upstream commit restores the workaround), then restart sshd; existing sessions are unaffected so this is a daemon restart, not a reboot. Until the package lands, disable password authentication (PasswordAuthentication no, keys only) on Alpine/musl hosts, which removes the exposure entirely. Inventory which hosts actually use musl without PAM before scheduling - glibc and PAM-enabled builds are not affected.

References

Related entries

All Kernel, userspace & hypervisor entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.