
Advisory and defensive analysis of CVE-2026-123158 (SSHhole), an OpenSSH password authentication bypass on musl libc systems, with detection commands and remediation guidance.
SSHhole
Security Research • Vulnerability Analysis • Defensive Testing
CVE-2026-123158, also known as SSHhole, is a password authentication bypass vulnerability affecting OpenSSH servers running on certain Linux configurations using musl libc without PAM support.
The vulnerability occurs because of an interaction between OpenSSH password verification and the error-handling behavior of musl libc's crypt() function.
Under specific account configurations, an attacker may authenticate using an incorrectly supplied password between 256 and 1024 characters.
Successful exploitation can result in unauthorized SSH access.
| Attribute | Details |
|---|---|
| CVE ID | CVE-2026-123158 |
| Name | SSHhole |
| Vendor | OpenBSD |
| Product | OpenSSH |
| Component | sshd |
| Vulnerability Type | Authentication Bypass |
| CWE | CWE-394 |
| CVSS Version | 3.1 |
| CVSS Score | 8.1 |
| Severity | High |
| Attack Vector | Network |
| Privileges Required | None |
| User Interaction | None |
| Affected Library | musl libc |
| Affected Environment | Linux without PAM |
| Fixed Version | OpenSSH 10.6p2 |
| Disclosure Date | November 5, 2026 |
The vulnerability requires a specific combination of conditions.
Potentially affected configurations:
*.Examples of potentially affected environments:
Important: The presence of musl libc alone does not establish vulnerability. All relevant conditions must be evaluated.
The issue involves the interaction between:
crypt() implementation.When a password exceeds musl's supported input length, crypt() can return * to indicate an error.
Some Unix account configurations also use * as the stored password field for accounts that cannot authenticate using a password.
In the affected OpenSSH authentication path, these values can be incorrectly interpreted as a successful password match.
The underlying problem can be represented conceptually:
Submitted password
|
v
OpenSSH password verification
|
v
musl crypt() function
|
v
Password exceeds supported length
|
v
Returns "*" as an error indicator
|
v
Stored account password field is "*"
|
v
Incorrect string comparison
|
v
Authentication bypass
This behavior depends on the affected account configuration and runtime environment.
Potential consequences include:
Note: Root access is not automatic. The resulting privileges depend on the account and system configuration.
The following commands are intended for authorized system auditing.
cat /etc/os-release
ssh -V
For the SSH server binary:
sshd -V 2>&1
ldd --version
On Alpine Linux, musl is the standard C library.
sudo sshd -T | grep -Ei 'usepam|passwordauthentication'
Expected configuration fields:
usepam no
passwordauthentication yes
These values indicate potentially relevant conditions, not confirmed exploitability.
apk info openssh-server
Compare the installed package revision against the official Alpine security advisory.
sudo grep 'Accepted password' /var/log/messages
Investigate unexpected successful password logins, especially involving accounts intended to use SSH keys only.
Upgrade to OpenSSH 10.6p2 or later, or install the corresponding security-patched package supplied by your Linux distribution.
Update installed packages:
sudo apk upgrade -U -a
Restart the SSH service:
sudo rc-service sshd restart
Verify the installed package revision after updating.
If immediate patching is not possible, disable SSH password authentication.
Edit:
sudo nano /etc/ssh/sshd_config
Set:
PasswordAuthentication no
Validate the configuration:
sudo sshd -t
Restart SSH:
sudo rc-service sshd restart
Warning: Confirm that SSH key-based access works before disabling password authentication. Keep an existing administrative session open while testing to avoid locking yourself out.
Suggested lab:
| Component | Environment |
|---|---|
| Attacker workstation | Kali Linux |
| Vulnerable test environment | Alpine Linux |
| SSH service | OpenSSH |
| C library | musl libc |
| Analysis | Linux authentication logs |
| Testing | Isolated virtual machine |
Only perform security testing against systems you own or have explicit permission to assess.