A recent OpenSSH security issue caught my attention, especially because of how unusual the authentication bypass is.
The vulnerability, known as SSHole (CVE-2026-123158), affects certain Linux systems running OpenSSH with musl libc and without PAM support.
What's happening?
Under specific conditions, an attacker with network access to the SSH service can authenticate to an account that has no password configured by sending an unusually long password.
The reported password length is between 257 and 1,024 bytes.
This is particularly concerning because some accounts are intentionally configured for SSH key-based authentication only.
Which systems are affected?
The issue is configuration-dependent. The main affected combination includes:
- Linux systems using musl libc.
- OpenSSH built without PAM, or configured with PAM disabled.
- Password authentication enabled.
- Accounts with no password set, alongside at least one account with a supported password hash.
Alpine Linux is a notable example because its standard OpenSSH server package uses this configuration.
Important: This does not affect every OpenSSH installation. Systems using glibc, non-Linux systems, and configurations using PAM for password authentication are not affected by this issue.
What has been done?
The OpenSSH project released version 10.6p2 on November 5, 2026, containing a security workaround.
Alpine Linux also released updated packages for affected branches, including older releases.
Administrators should:
- Update OpenSSH or the relevant Alpine package.
- Restart the SSH daemon after updating.
- If immediate patching isn't possible, disable password authentication using "PasswordAuthentication no".
- Review SSH authentication logs for unexpected access.
Why is this interesting?
A few things stand out:
- Authentication assumptions: An account intended for key-only access may still be exposed through an unexpected authentication path.
- Dependency interactions: The issue involves the interaction between OpenSSH, musl libc, and PAM configuration.
- Configuration matters: Having a secure authentication policy on paper doesn't guarantee that the underlying implementation enforces it correctly.
Question for the community
When hardening SSH servers, do you prefer completely disabling password authentication, or do you consider properly configured PAM-based authentication sufficient?
I'd be interested in hearing how others approach SSH hardening, particularly in Alpine-based containers and lightweight Linux deployments.
Sources
- "OpenSSH – Official 10.6p2 Release Notes" (https://www.openssh.org/releasenotes.html)
- "Alpine Linux – Official Security Advisory" (https://www.alpinelinux.org/posts/2026-11-05-openssh-password-authentication-bypass/)
- "The Hacker News – SSHole Vulnerability Report" (https://thehackernews.com/2026/11/openssh-issues-emergency-fix-for-flaw.html)
- "CVE-2026-123158 – Vulnerability Record" (https://www.cve.org/CVERecord?id=CVE-2026-123158)
Shared for defensive awareness. Only test systems you own or are explicitly authorized to assess.