OpenSSH 10.6p2 fixes a password bypass on Alpine and other musl Linux. Check if your SSH server is one of them
On 5 Nov 2026 OpenSSH released 10.6p2 with a workaround for a bug nicknamed "*sshole". On Linux that uses musl libc (Alpine, OpenWrt, Buildroot, Yocto) with PAM off, an oversized password can log in to an account that should only accept keys. Glibc systems such as Debian and Ubuntu are not affected. Since 7 Nov it is being exploited in the wild and CISA lists it as exploited (CVE-2026-123158). Who is at risk and what to do.
Updated 10 Nov 2026: see what changedHow urgent
Act now
Who is affected
Servers and containers that run an OpenSSH server on a musl-based Linux (Alpine, OpenWrt, Buildroot, Yocto) with PAM disabled and SSH password login enabled. Not affected, per the researcher and BleepingComputer: Debian, Ubuntu, Fedora and other glibc systems, PAM setups, Dropbear
What to do
If you run sshd on Alpine or another musl system, update OpenSSH to 10.6p2 (on Alpine, apk upgrade openssh). If you cannot update, set PasswordAuthentication no and restart sshd. Then look in the logs for password logins to accounts that should only use keys
Published 6 Nov 2026 · Sources last checked 10 Nov 2026No. 57 / 87
Updates, follow-ups and corrections
- Update · 10 Nov 2026. The bug is now exploited in the wild. CISA added CVE-2026-123158 (OpenSSH, "Unexpected Status Code or Return Value") to its Known Exploited Vulnerabilities catalog on 9 Nov (read directly in CISA's catalog). BleepingComputer (9 Nov, read directly) reports that GreyNoise recorded the first successful exploitation on 7 Nov at 00:46 UTC, about 40 hours after the fix, and that Previdian saw 20 attempts from 13 IP addresses in nine countries; we did not read the GreyNoise or Previdian reports themselves. In one GreyNoise case an attacker got root and installed a Python remote-control agent called TAC Agent. Severity raised from *week* to *act*. The fix is unchanged: OpenSSH 10.6p2, or turn password login off.
- Update · 6 Nov 2026. First version of the story, based on the OpenSSH 10.6p2 release notes (5 Nov 2026) and the researcher's write-up, both read directly, plus BleepingComputer's report. No CVE number has been published for the musl issue in the sources we read. We did not test the bug ourselves.
We keep the original text. When something changes, when we follow a story, or when we get something wrong, we add a dated note here instead of editing silently.
What happened
On 5 November 2026 the OpenSSH project released 10.6p2. Its notes say it contains a *"critical security workaround"* for Linux systems that use musl libc with PAM disabled. The maintainers say the root cause is outside sshd, but that sshd can be used to exploitExploit A piece of code or a technique that takes advantage of a specific flaw to get something the attacker should not get. Tap again to open the glossary it and can avoid it. The bug was reported by Özgün Kültekin, who calls it "*sshole".
How it works, per the researcher: on musl, the password-hashing function returns the text * when it fails, and it fails for any password longer than 256 bytes. An account whose stored password is also * (the usual way to say "no password, keys only") then looks like a match. So an oversized password can log in to an account that was meant to accept only SSH keys.
Who is affected
All of these have to be true, per the researcher and BleepingComputer:
- OpenSSH server on musl libc: Alpine, OpenWrt, Buildroot, Yocto and many container images built on them.
- PAM off (the default in Alpine's openssh-server package).
- SSH password login on (the default).
- At least one account whose password is
*(key-only users, root on Alpine), and another account with a real password.
Debian, Ubuntu, Fedora and other glibc systems, PAM setups and Dropbear are not affected. BleepingComputer notes Alpine's official AWS and Azure images have a default alpine user with passwordless doas, which would mean root. Most containers do not run an SSH server at all, so this mostly matters for servers, routers and appliances.
Is it being exploited?
Update, 10 Nov 2026: yes. CISA added CVE-2026-123158 to its exploited-vulnerabilities catalog on 9 November. BleepingComputer, citing GreyNoise, reports the first successful exploitation on 7 November at 00:46 UTC, about 40 hours after the fix, and 16 successful attack chains against GreyNoise-protected networks from six addresses (GreyNoise says these are not representative of all activity). Previdian counted 20 attempts from 13 addresses in nine countries. After getting in, attackers looked around the system and containers, queried cloud metadata services, tried to read password hashes and root SSH keys and to add their own keys. In one case an attacker reached root and installed TAC Agent, a Python remote-control agent that talked to a command server at tac.vpnla[.]org; in that case it could not reach it. We have not read the GreyNoise or Previdian reports, only BleepingComputer's account of them.
What to do
- Check whether you run sshd on a musl system.
ldd --versionon Alpine reports musl. If you use Debian or Ubuntu, you are not in this group. - Update to OpenSSH 10.6p2. On Alpine:
apk upgrade openssh. - If you cannot update, turn off password login:
PasswordAuthentication noin the sshd config, then restart sshd. Key-only login is better anyway. - Check the logs for successful password logins to accounts that should only use keys. BleepingComputer suggests
grep "Accepted password" /var/log/messageson Alpine. - Look for signs of a break-in: unexpected SSH keys in
authorized_keys, a TAC Agent file or a new startup service, and connections to tac.vpnla[.]org. If you find any, treat the server as compromised. - Do not leave sshd open to the whole internet if you do not need to: restrict it by address or use a VPNVPN A private encrypted tunnel between your device and a network, so traffic does not travel in the open. Tap again to open the glossary.
What we could not confirm
The CVECVE A public ID number, like CVE-2026-12345, given to one specific security flaw so everyone can talk about the same bug. Tap again to open the glossary number, CVE-2026-123158, comes from CISA's catalog and BleepingComputer; the OpenSSH release notes and the researcher's page did not give one. We did not test the bug or the researcher's checker tool. The release notes call it a workaround because the maintainers place the fault in musl, so a fix on the musl side may follow; we have not seen one. We have not read the GreyNoise and Previdian reports, so the attack details above rely on BleepingComputer, which gives no affected OpenSSH version range beyond the 10.6p2 fix.
Watch the short video
The video loads from YouTube (privacy-enhanced mode) only when you press play.
Comments
No account needed. Add a nickname if you like, or leave it empty to comment anonymously. Comments are reviewed before they appear. Links are not allowed.
We store your comment, your nickname and a scrambled form of your connection that we use only to limit spam. We do not store your IP address or set cookies. Cloudflare Turnstile checks that you are not a bot.
Sources and verification
- OpenSSH: release notes for 10.6p2 (5 Nov 2026, official, read directly; it calls this a critical security workaround) (opens in a new tab)
- Özgün Kültekin: sshhole.com (researcher's write-up, read directly) (opens in a new tab)
- CISA: Known Exploited Vulnerabilities catalog, CVE-2026-123158 added 9 Nov 2026 (read directly) (opens in a new tab)
- BleepingComputer: Hackers exploit SSHole OpenSSH flaw to breach Linux systems (9 Nov 2026, read directly; it cites GreyNoise and Previdian) (opens in a new tab)
- BleepingComputer: OpenSSH flaw lets attackers log into password-disabled Linux accounts (5 Nov 2026) (opens in a new tab)
We use primary sources first and say when we rely on a news report. Dates are the day we last checked each source.
Spotted a mistake? Email [email protected] and we will correct it and note the change.