An old interaction in password verification can allow an SSH login without knowing the account's actual password. On 5 November 2026, OpenSSH released 10.6p2, Alpine Linux shipped patched packages and France's CERT-FR issued a dedicated security alert. The flaw is tracked as CVE-2026-123158.
Key takeaway: not every OpenSSH server is vulnerable. Exploitation requires musl without PAM, password authentication enabled, an accessible account whose stored password field is *, and another account with a $5$ or $6$ password hash. Alpine administrators running sshd should install the patched package and restart the daemon. Where patching is not immediately possible, disabling password authentication can mitigate the flaw—but verify key-based access first.
Who is vulnerable, and who is not?
Alpine's 5 November advisory identifies these conditions:
- the standard Alpine openssh-server build without PAM, or
openssh-server-pamconfigured withUsePAM no; - an effective
PasswordAuthentication yessetting; - an SSH-accessible account with
*in its stored password field, a pattern found on some key-only accounts; - at least one other local account with a
$5$(SHA-256) or$6$(SHA-512) password hash.
In such environments, a password of a particular length can be accepted despite not matching the account's legitimate secret. An exposed technical account may be enough for an attacker to gain a shell, and its permissions or delegated privileges determine the subsequent impact.
The same advisory identifies scenarios not exposed to this path: containers without a running sshd, servers with effective PasswordAuthentication no, PAM-enabled servers using UsePAM yes, truly locked accounts with a ! password field, and hosts without any $-style password hash. Standard glibc-based Ubuntu and Debian installations do not match the particular musl condition discussed here.
Root cause: an error marker mistaken for a password match
In non-PAM mode, OpenSSH uses the C library's crypt() function to compare a candidate password with a stored representation. An older fallback mechanism may borrow a salt from another account when the target account's stored field is too short to provide a usable salt. This design was partly intended to avoid behavior that could disclose whether a user exists.
For musl, however, crypt() can return * as an error indicator when an input exceeds 256 bytes. The target account may also contain the literal value * in its password field. A faulty comparison may then treat an error result as a valid match. This is not a break of the SSH cryptographic protocol: it is a semantic collision between an error sentinel and an account-state marker inside an authentication workflow.
The OpenSSH 10.6p2 release fixes the dangerous condition in sshd, and Alpine backported the change to supported and several older branches. The deeper lesson is that security assumptions about library return values can fail when implementation details change.
Patched Alpine packages
| Alpine branch | First fixed OpenSSH package |
|---|---|
| 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 |
| 3.19 | 9.6_p1-r3 |
| 3.18 | 9.3_p2-r4 |
| 3.17 | 9.1_p1-r7 |
| 3.16 | 9.0_p1-r6 |
Alpine released versions 3.24.4, 3.23.8, 3.22.8 and 3.21.10 on 5 November. Fixed packages were also made available for older branches, but Alpine 3.21 and earlier are out of regular support. An emergency fix does not eliminate the need to migrate such systems to a supported branch.
Do not rely solely on the upstream version printed by an SSH banner. A patched Alpine package can retain an older upstream version while carrying a security backport. And a package upgrade alone does not replace an already running sshd process.
Practical hardening and audit
1. Inventory actual exposure
Find Alpine hosts running an SSH service and identify their release branch, server package, network exposure and effective authentication policy. On authorized systems, these commands help gather the initial facts:
cat /etc/alpine-release
apk info -v openssh-server openssh-server-pam
sshd -T | grep -Ei 'passwordauthentication|usepam|permitrootlogin'
For configurations using Match blocks, review user- and source-specific effective settings rather than assuming the global sshd -T output represents every login. Inspect account state without disseminating password hash contents.
2. Install patched packages and restart SSH
With a recovery or console path available, use the distribution's upgrade procedure:
apk upgrade -U -a
rc-service sshd restart
apk info -v openssh-server openssh-server-pam
Then verify the actual fixed server package revision, daemon status and legitimate connections. Keep an established administration session open during remote changes where possible.
3. Mitigate if immediate patching is impossible
Alpine advises applying PasswordAuthentication no and restarting sshd. First verify that key-based login succeeds from a new session. Confirm that the rule is effective for the relevant users and sources. Network filtering, least privilege and segmentation are useful containment measures, but they are not substitutes for a permanent fix.
Investigating a possible intrusion
Alpine recommends checking /var/log/messages for Accepted password for events involving accounts that should only use SSH keys. Correlate these logins with source addresses, timelines, doas activity, unexpected users, new authorized keys, filesystem modifications and outbound connections.
Such an event is a lead, not stand-alone proof of exploitation. Preserve logs and relevant system state before destructive remediation. For authorized investigations, distinguish attempted access, successful authentication and confirmed unauthorized activity.
Confirmed exposure versus real-world exploitation
OpenSSH released a security fix, Alpine supplied packages and the French CERT published an alert on 5 November 2026. Public reproductions demonstrate the vulnerability. But the official material reviewed as of 6 November 2026 does not establish a confirmed in-the-wild campaign or a reliable count of compromised servers.
That uncertainty does not make patching optional. When the precise preconditions are present, unauthorized password-based access is a confirmed technical risk.
Why it matters beyond Alpine
For GLOV Consulting, this is a reminder that an effective vulnerability program tracks effective configuration, libc implementation, vendor backports and running processes, not simply upstream version strings. Operators of infrastructure services such as those presented by Snow-Fall face the same requirements around administrative access, secure defaults and recoverability.
The dependency-management lesson also connects to our coverage of Node2Shell and Elastic Synthetics and PHP2Shell security updates. These are different vulnerabilities, but each illustrates the importance of knowing what code and configuration actually run in production.
Information reviewed on 6 November 2026. No compromise of GLOV Solutions infrastructure is alleged.
Official sources and technical research
- CERT-FR — CERTFR-2026-ALE-015 OpenSSH alert (5 November 2026)
- OpenSSH — 10.6p2 release notes (5 November 2026)
- Alpine Linux — security advisory and exposure criteria (5 November 2026)
- Alpine Linux — patched release announcement (5 November 2026)
- GitHub Advisory Database — CVE-2026-123158 / GHSA-4fcc-vm97-gx3x
- Wakefield — technical investigation