OpenSSH SSHole Authentication Bypass Actively Exploited Within Hours
Threat actors began exploiting a critical OpenSSH authentication bypass vulnerability within hours of its disclosure on November 5, 2026. The flaw, tracked as CVE-2026-123158 and nicknamed SSHole, lets unauthenticated attackers log into passwordless accounts on Alpine Linux and other musl-based systems by sending an oversized password. Previdian has already confirmed successful root access on a honeypot.
What Happened: OpenSSH SSHole Authentication Bypass Under Active Attack
On November 5, 2026, the OpenSSH project released version 10.6p2 to fix a high-severity flaw that had gone unnoticed for years. Security researcher Özgün Kültekin discovered that under specific conditions, OpenSSH running on systems using the musl C library would treat a failed password hash as a successful login.
Furthermore, threat intelligence firm Previdian reported that exploitation began less than nine hours after the CVE was published. Attackers used a single Japan-based IP address (89.116.89[.]18) to send oversized passwords and gain access to a honeypot running real Alpine Linux and OpenSSH. The attackers ran reconnaissance commands including id, uname, and hostname through non-interactive SSH sessions.
In addition, Alpine Linux published its own security advisory the same day, warning that the vulnerability is trivial to exploit. The Alpine team stated: “An attacker who can reach your SSH port can log in without knowing any password. It takes one connection, works every time, and needs no retries.”
Technical Details of the SSHole Vulnerability
The root cause of CVE-2026-123158 lies in how OpenSSH interacts with musl’s crypt() function when handling accounts that have no usable password hash. On affected systems, password-disabled accounts store an asterisk (*) in their password field within /etc/shadow.
Back in 2016, OpenSSH introduced a patch for CVE-2016-6210 that changed how sshd handled accounts without valid password hashes. The daemon began borrowing another account’s salt and hashing the supplied password anyway. However, musl’s crypt() function has refused SHA-256 and SHA-512 passwords longer than 256 bytes since 2012. When it encounters an oversized password, it fails and returns * — the exact same character stored for passwordless accounts. OpenSSH then incorrectly interprets this match as successful authentication.
Consequently, an attacker can authenticate to certain accounts by sending any password between 257 and 1,024 bytes long. It is important to note that this flaw does not bypass passwords on accounts with valid password hashes. Successful exploitation requires:
- A system using the musl C library without PAM password checks
- At least one account with
*as its password hash - Password authentication enabled in sshd (the OpenSSH default)
- At least one other local account with a valid password hash
Systems Confirmed Affected
- Alpine Linux default openssh-server package (all branches from 3.16 to edge)
- Alpine tiny-cloud AWS and Azure images (versions 3.18.11 through 3.24.3)
- OpenWrt, Buildroot, and Yocto musl-based builds
- Many Docker images based on Alpine Linux
Systems Confirmed Not Affected
- Linux distributions using glibc (Debian, Ubuntu, Fedora, RHEL, etc.)
- Systems that check passwords through PAM
- Dropbear SSH implementations
- OpenBSD systems
- Non-Linux operating systems
Business and Operational Impact
A successful SSHole attack grants the attacker access with the compromised account’s existing permissions. The impact varies dramatically depending on which account is targeted:
- Root compromise on cloud images: Alpine’s official AWS and Azure images ship with a default
alpineuser that has passwordlessdoasprivileges. An attacker hitting this account effectively gains root. - Deployment credential exposure: Compromised SSH access may expose CI/CD credentials, application secrets, and connected infrastructure.
- Lateral movement: Unauthorized SSH access enables attackers to pivot through networks, escalate privileges, and maintain persistence.
- Container and DevOps risk: A significant portion of Docker containers and Kubernetes clusters use Alpine as a base image, expanding the attack surface.
Moreover, the trivial nature of exploitation means attackers can automate attacks at scale. Ryan Dewhurst of Previdian noted that AI-assisted tooling is shrinking the time between disclosure and exploitation, calling this vulnerability “particularly trivial to exploit.”
Mitigation and Recommendations
Immediate Actions for Defenders
- Patch immediately: Upgrade to OpenSSH 10.6p2 or install your distribution’s patched package. Alpine has published fixes for all supported branches.
- Restart sshd: Installing the update does not restart the running daemon. Restart sshd after patching to ensure the fixed binary is active.
- Disable password authentication: As an interim measure, set
PasswordAuthentication=noinsshd_configand reload the service. This blocks the attack vector entirely. - Hunt for indicators of compromise: Search
/var/log/messagesfor"Accepted password for"entries involving accounts that should not accept passwords (alpine, root, key-only users). - Review system integrity: Check for newly created users, unauthorized authorized_keys files, and unexpected
doasusage. If you cannot rule out a login, treat the machine as compromised.
Long-Term Hardening
Organizations running musl-based systems should evaluate their SSH exposure and authentication policies. Consider migrating key-only accounts to certificate-based authentication, and audit container registries for outdated Alpine-based images that may still carry vulnerable OpenSSH versions.
Bottom line: CVE-2026-123158 is actively exploited, easy to trigger, and can deliver root access on widely used cloud images. Patch and restart sshd now, then hunt for signs of compromise in your logs.
Incident Summary
| CVE ID / Incident: | CVE-2026-123158 (SSHole) |
| CVSS Score: | 8.1 (High) |
| Affected Systems: | OpenSSH on musl-based Linux (Alpine Linux, OpenWrt, Buildroot, Yocto, Alpine cloud images, many Docker containers) |
| Disclosure Date: | November 5, 2026 |
| Patch Status: | Fixed in OpenSSH 10.6p2; Alpine packages patched same day |
| Exploitation Status: | Active exploitation confirmed by Previdian within 9 hours of disclosure |
| Attacker TTPs: | Oversized password (257-1024 bytes) to bypass authentication; reconnaissance via non-interactive SSH |
References
- The Hacker News, “Hackers Target OpenSSH SSHole Flaw Within Hours of Disclosure, Gain Root on Honeypot,” November 6, 2026, https://thehackernews.com/2026/11/hackers-exploited-openssh-sshole-flaw.html, accessed November 6, 2026.
- Help Net Security, “OpenSSH flaw exploited in the wild just hours after disclosure (CVE-2026-123158),” November 6, 2026, https://www.helpnetsecurity.com/2026/11/06/openssh-sshole-cve-2026-123158-exploitation/, accessed November 6, 2026.
- Alpine Linux, “OpenSSH password authentication bypass,” November 5, 2026, https://alpinelinux.org/posts/2026-11-05-openssh-password-authentication-bypass/, accessed November 6, 2026.
- Özgün Kültekin, “sshhole,” November 5, 2026, https://sshhole.com/, accessed November 6, 2026.
- OpenSSH Project, “OpenSSH 10.6p2 Release Notes,” November 5, 2026, https://www.openssh.org/releasenotes.html#10.6p2, accessed November 6, 2026.
- Previdian, “CVE-2026-123158 Telemetry Summary,” November 6, 2026, https://previdian.com/CVE-2026-123158#summary, accessed November 6, 2026.
- SOCRadar, “SSHole: OpenSSH Password Bypass on Alpine Linux,” November 6, 2026, https://socradar.io/blog/sshole-openssh-password-bypass-alpine/, accessed November 6, 2026.
- Safe Security, “SSHole: High-Severity OpenSSH Vulnerability Turns Disabled Passwords Into Unauthorized Access,” November 6, 2026, https://safe.security/resources/blog/sshole-high-severity-openssh-vulnerability-turns-disabled-passwords-into-unauthorized-access/, accessed November 6, 2026.