A password login can succeed against an Alpine Linux SSH account that was meant to accept keys only. The CVE Program record assigns the flaw CVE-2026-123158 to OpenSSH before 10.6p2 on Linux with musl libc and PAM disabled. Anyone who can reach a vulnerable sshd and satisfy the account conditions can gain that account’s access. Alpine hosts and containers that run and expose OpenSSH deserve a package check now. StepSecurity found no confirmed exploitation in the original disclosure or vendor advisories it reviewed on November 6.
OpenSSH released 10.6p2 on November 5 with a workaround in sshd, and the Alpine security tracker lists fixed openssh revisions for its branches. Read the installed Alpine package revision and restart the running daemon after upgrading. A backport can leave the server banner showing an earlier upstream version even when the installed package contains the fix.
Musl error matches locked password field
On affected systems, the target account’s shadow password field contains *, which normally prevents password login. The vulnerable OpenSSH non-PAM path borrows a salt from another local account with a real SHA-crypt password hash. For an overlong submitted password, musl’s crypt() returns * as an error value. The old sshd comparison treats that value as if it were a calculated hash and matches it to the target account’s *. That is how a password reaches an account whose intended login method is a key. The patched OpenSSH path rejects implausibly short stored hashes before the comparison.
The account must also be permitted to log in by SSH, PasswordAuthentication must be yes, and the system must have that separate local SHA-crypt hash for the borrowed salt. Direct root login additionally requires PermitRootLogin yes; the default prohibit-password setting blocks that root route. PAM-backed password verification takes a different path. Prioritize musl-based sshd installations, including Alpine images used for remote debugging, that meet these account and policy conditions.
The official Alpine tiny-cloud image includes a key-only alpine account with passwordless doas. StepSecurity says the fresh image is safe on first boot because there is no other local account with a real SHA-crypt hash. Adding a password-hashed local account supplies the salt source that the vulnerable non-PAM path uses. Check the account state on the deployed image or host, including whether * denotes an SSH-eligible account. An empty shadow field represents a different password configuration and needs its own review.
The lab exposed a second-attempt log pattern
StepSecurity reproduced the bypass against an Alpine 3.24 VM and a container with published SSH access using the pre-fix 10.3_p1-r1 package. In those tests a first password attempt failed; a later attempt in the same connection produced an Accepted password event for a key-only account. The researcher then upgraded to 10.3_p1-r2, restarted sshd, and observed rejection of the same class of attempts while normal logins still worked. A PAM-flavor test with UsePAM yes also rejected the bypass.
For incident review, correlate Failed password followed by Accepted password for a key-only account in the same SSH session. An Accepted password for an account whose shadow field is * warrants investigation even if the preceding failure is unavailable. Preserve the session’s source address, account name, and surrounding authentication logs. StepSecurity found that a version-string-only community check falsely called its patched Alpine host exposed: its 10.3_p1-r2 package still advertised upstream OpenSSH_10.3p1.
A single-prompt network scanner can miss the vulnerable configuration StepSecurity tested, since the first attempt in its VM and container was rejected. Its client and askpass helper also stopped delivering some upper-length inputs before they reached sshd, while shorter test inputs still reached the server. For exposure triage, use the installed package revision, UsePAM and PasswordAuthentication settings, and the two account conditions alongside any scan result. For an investigation, a successful password event against a key-only account is the stronger signal, even when log retention has lost the earlier failure.
Check Alpine revisions and restart sshd
Inventory Alpine hosts and stored container images that install openssh-server, especially images with an exposed SSH service or pinned package layers. Run apk info -v openssh-server on the target host; for the PAM flavor use apk info -v openssh-server-pam. Compare the returned revision against the Alpine tracker: edge 10.6_p2-r0, 3.24 10.3_p1-r2, 3.23 10.2_p1-r1, 3.22 10.0_p1-r11, 3.21 9.9_p2-r1, 3.20 9.7_p1-r6, and 3.19 9.6_p1-r3. For other branches, use the branch’s published security package data. Rebuild older container layers from updated repositories, upgrade affected installations, and restart the running sshd after installing the fix.
A fresh package installation from the Alpine 3.24 repositories StepSecurity checked fetched the patched openssh-server; images pinned before November 5 can still carry 10.3_p1-r1 in cached CI layers, internal registries, or package mirrors. Check the installed package inside the image you actually deploy; its base-image tag can miss an older cached layer. If an Alpine runner or debugging container has no operational reason to serve SSH, remove sshd from the image and its published SSH port from the deployment. That change takes the reachable password-authentication path out of the container altogether.
Confirm the package and login policy
Where password login is unnecessary, set PasswordAuthentication no after confirming key access, then reload or restart sshd and confirm the effective setting for the affected account, including any Match rules. For a host that must retain password logins before an upgrade, StepSecurity’s lab found the PAM flavor with UsePAM yes blocked this path; validate ordinary logins before ending your current administrative session. Check local SSH-eligible accounts for a * shadow field and review successful password events for those accounts. Patch or change the policy, then verify the installed Alpine package revision, running service and effective password-authentication setting. The server’s upstream version banner alone can miss an Alpine backport.