Earlier this month, security researchers disclosed CVE-2026-123158 — nicknamed "SSHole" — an 8.1-severity flaw that lets an attacker log into certain Linux systems with no valid password at all, simply by typing an unusually long one. Threat-intel firm Previdian says it caught real exploitation attempts starting less than nine hours after the flaw became public, and confirmed an attacker reaching full root access on a honeypot server (The Hacker News, 2026; Help Net Security, 2026). If your business runs Linux servers, cloud VMs, or Docker containers, it's worth a few minutes to check whether this affects you."SSHole": A 10-Year-Old Fix Just Opened a Backdoor Into Some Linux Servers

What Actually Causes This?

The root cause traces back a decade. A 2016 OpenSSH fix for an unrelated bug made the login process hash a supplied password even when the target account has no password set — and on systems using the musl C library (instead of the more common glibc), that hashing function returns the same placeholder value, "*", for both "no password set" and "password too long to process." Submit a password longer than 256 bytes to an account with no password hash, and the two placeholder values match. The login succeeds.

Who's Actually Exposed?

This isn't every Linux server. It specifically affects OpenSSH installations on musl-based systems that aren't using PAM for authentication — most notably Alpine Linux's default SSH configuration, plus OpenWrt, Buildroot, and Yocto-based systems. Alpine is also the base image for a huge share of lightweight Docker containers, so any business running containerized infrastructure may have more exposure here than it realizes. Mainstream distributions like Debian, Ubuntu, and Fedora (which use glibc) are reported as unaffected, as are systems that authenticate through PAM.

Is a Patch Available?

Yes. OpenSSH 10.6p2, released November 5, fixes it, and Alpine pushed patched packages the same day across its supported branches. One catch worth repeating: installing the patch doesn't change a server that's already running — sshd has to be restarted before the fix takes effect.

What Should a Business Do?

Patch OpenSSH to 10.6p2 (or your distribution's equivalent) and restart the SSH service — don't stop at the install step. Where that's not immediately possible, OpenSSH's own developers recommend disabling password-based SSH logins entirely in the meantime. It's also worth checking your server logs for unexpected "Accepted password" entries on accounts that shouldn't be accepting passwords at all, like root or key-only service accounts — that's the specific sign this flaw leaves behind.