OpenSSH SSHole (CVE-2026-123158): Attackers Gain Root Within Hours of Disclosure
Dr. Abeer Alshammari · Published 11/6/2026 · Updated 11/7/2026
Previdian reports active exploitation attempts and a confirmed root login on a honeypot. The flaw is not described here as listed in CISA KEV; check the catalog for the current status.
What happened
OpenSSH disclosed CVE-2026-123158, nicknamed SSHole, and released version 10.6p2 to fix it. The bug lets an unauthenticated attacker sign in to accounts whose password field holds an asterisk, which is how many systems mark an account that has no password. The flaw was found by researcher Ozgun Kultekin.
How it works
A 2016 change meant to stop username enumeration left an edge case. When a supplied password is between 257 and 1,024 bytes long, the hashing step fails and returns an asterisk. The server then compares that asterisk with the asterisk stored for the account and treats the two as a match, so the login succeeds. Accounts with real password hashes are not affected.
Who is affected
Linux systems running OpenSSH on the musl C library with PAM disabled, which includes the default openssh-server configuration on Alpine Linux. Dropbear, glibc-based distributions, non-Linux systems, and systems that check passwords through PAM are not affected. Alpine Linux is common in containers, so exposure is often inside images rather than on named servers.
Technical impact
| Field | Detail |
|---|---|
| CVE | CVE-2026-123158 (SSHole) |
| CVSS | 8.1 |
| Vulnerability type | Authentication bypass via oversized password |
| Precondition | An account with an asterisk as its password hash, such as a key-only account |
| Fixed in | OpenSSH 10.6p2 or the distribution package |
| Observed exploitation | First attempt under nine hours after publication; root access confirmed on a honeypot |
Governance impact
The time between disclosure and the first attack was under nine hours. Patch processes measured in weeks cannot keep up with that pace for internet-facing services, so the control to test is how fast a critical fix reaches containers and base images, not only servers.
What security teams should do
- Inventory Alpine and other musl-based hosts and container images that run sshd
- Upgrade to OpenSSH 10.6p2 or the patched distribution package, then restart sshd
- Search the logs for "Accepted password for" on accounts that should never accept a password login
- Review doas use, recently created users, files, and authorized keys on exposed machines
- If a login cannot be ruled out, treat the machine as compromised
What executives should know
This is a fast-moving exposure in a widely used remote access tool. The business question is whether the organization can find every affected system and patch it within a day, including those packaged inside container images.
Disclosure to exploitation is now measured in hours. Ask who owns the list of internet-facing remote access services and how long a critical fix takes to reach them. If the honest answer is weeks, that gap is the control to fix first.
Many GCC organizations run Linux workloads in containers and cloud images. Check base images for Alpine rather than assuming server patching covers them.
Sources
- [1]Alpine Linux: OpenSSH password authentication bypass — Alpine Linux (11/5/2026)Accessed 11/7/2026
- [2]OpenSSH 10.6p2 release notes — OpenSSH (11/5/2026)Accessed 11/7/2026
- [3]CVE-2026-123158 — NIST National Vulnerability Database (11/5/2026)Accessed 11/7/2026
- [4]CVE-2026-123158 exploitation telemetry — Previdian (11/6/2026)Accessed 11/7/2026
- [5]Hackers Target OpenSSH SSHole Flaw Within Hours of Disclosure — The Hacker News (11/6/2026)Accessed 11/7/2026
Try it yourself
An interactive CyberAbeer experience for this topic is in development.
Coming soon