---
title: "SSHole Checker (CVE-2026-123158) — OpenSSH Bypass on Alpine | fbuff"
description: "Why a long password logs in to Alpine servers (SSHole, CVE-2026-123158), who is at risk, the fixed openssh package per branch, and how to check or close it."
url: https://fbuff.com/tools/sshole-checker/
---

## How to use

1. Read the first section below: it explains in plain words why a very long password lets an attacker in.
2. On the server, run the seven read-only commands next to the box as root (or copy them all at once) and paste the output. The account check prints two numbers, never user names or password hashes.
3. Read the verdict: Exposed, Vulnerable, Password login off, Patched or Not affected. The table under it shows what the checker found.
4. Update openssh and restart sshd. If you can't update today, turn password logins off with Alpine's commands under the result, after testing that your SSH key works.

## What causes SSHole (CVE-2026-123158), in plain words

When sshd is built without PAM, as Alpine's openssh-server package is, it checks a password itself. It runs the attempt through crypt(), the C library function that turns a password into the same kind of hash stored in /etc/shadow, and compares the two strings. If they match, you are in.

Accounts that have no password store a single * in that field. That is normal for key-only users and for root on Alpine, which ships as root:* since about 3.16. Such a field is too short to hold a salt, so sshd borrows the salt of another account that does have a $5$ or $6$ password hash.

The trap is in musl, the C library Alpine uses. When the password given to crypt() is longer than 256 bytes, musl's crypt() fails, and the value it returns to signal that failure is the string *. sshd then compares * with the stored * and sees a match. Any password between 257 and 1,024 bytes logs in to an account that has no password. One connection is enough, every time, with no guessing.

Think of a door lock that, when you push in a key far too long for it, shows the same green light it shows for the right key. The lock isn't broken in the usual way; its error signal just looks exactly like success.

## Who is affected

All of these must be true. The server runs sshd built against musl libc without PAM: Alpine's openssh-server, or openssh-server-pam with UsePAM no. PasswordAuthentication is yes, which is the OpenSSH default. At least one account that can log in has * as its password field. And at least one other local account has a $5$ or $6$ password hash, because that is where the borrowed salt comes from.

Root is protected by the default PermitRootLogin prohibit-password, but that does not help when a key-only user can become root through doas. Alpine's official tiny-cloud images from 3.18.11 through 3.24.3 ship an alpine user with a * field and passwordless doas. They are safe on first boot and become exploitable as soon as anyone sets a password on the machine.

Not affected: containers that don't run sshd, servers with PasswordAuthentication no, openssh-server-pam with UsePAM yes, locked accounts (! in the password field), and cloud images set up with cloud-init, which writes PasswordAuthentication no.

## Why Debian, Ubuntu and RHEL are not at risk

The bug needs musl's crypt() and sshd's own password check. Debian, Ubuntu, Red Hat and most other mainstream distributions use glibc and build sshd with PAM turned on, so neither condition holds. Debian's tracker still lists bookworm and trixie as "vulnerable" because their openssh is older than 10.6p2, but rates the issue unimportant. Upgrade when the package arrives; there is no emergency on a glibc system.

Other musl systems, such as Void Linux musl or a self-built OpenSSH on a musl toolchain, are affected if they also run without PAM. For them the upstream release OpenSSH 10.6p2 is the fix.

## Fixed versions

OpenSSH 10.6p2 (November 5, 2026) changes sshd so the error value can no longer pass as a match. Alpine backported the same change to every branch back to 3.16 without changing the upstream number, so ssh -V still prints the old version on a fixed Alpine server. Check the package release (the -rN part) instead.

| Alpine branch | Fixed openssh package |
| --- | --- |
| edge | 10.6_p2-r0 |
| 3.24 | 10.3_p1-r2 |
| 3.23 | 10.2_p1-r1 |
| 3.22 | 10.0_p1-r11 |
| 3.21 | 9.9_p2-r1 |
| 3.20 | 9.7_p1-r6 |
| 3.19 | 9.6_p1-r3 |
| 3.18 | 9.3_p2-r4 |
| 3.17 | 9.1_p1-r7 |
| 3.16 | 9.0_p1-r6 |

## Ways to protect a server

Patch and restart: apk upgrade -U -a, then rc-service sshd restart. Upgrading the package does not replace the sshd that is already running; until you restart it, the hole stays open. Point releases 3.21.10, 3.22.8, 3.23.8 and 3.24.4 include the fix, so new images built from them are safe.

Turn off password logins: PasswordAuthentication no closes the hole completely. Alpine's commands under the result do it with a drop-in file and a sed on sshd_config, keep a backup, and print the setting so you can confirm it. Test a key login in a second session before you close the first.

Lock accounts that should never log in with a password: a ! in the password field (passwd -l) locks the account. Remove passwords you set only for the console if nobody uses them.

Shrink who can reach port 22: allow SSH only from your office, VPN or bastion addresses at the firewall or cloud security group.

## Was I attacked?

Look in /var/log/messages for sshd lines reading Accepted password for an account that has no password: alpine, root or any key-only user. Then review doas use, new users, new files in home directories and changes to authorized_keys. If you cannot rule out a login, treat the machine as compromised and rebuild it from a known-good image.

## Timeline

| Date (2026) | Event |
| --- | --- |
| November 5 | OpenSSH 10.6p2 released with a critical security workaround for musl systems without PAM; Alpine publishes its advisory and fixed packages for edge and 3.16 to 3.24 |
| November 6 | Help Net Security reports attacks in the wild within hours of disclosure |
| November | CVE-2026-123158 assigned; CISA adds it to the Known Exploited Vulnerabilities catalog |

## Frequently asked questions

### Is it called SSHole or sshhole?

Both. Write-ups use SSHole, sshole and sshhole for the same bug, CVE-2026-123158. The reproduction labs and the sshhole.com page use the double-h spelling.

### ssh -V on my Alpine server still shows an old version. Is it unpatched?

Not necessarily. Alpine backports the fix and keeps the upstream number, so ssh -V can't tell. Compare the openssh-server package release from apk info -v with the table above, for example 10.0_p1-r11 or later on 3.22.

### I only use SSH keys. Am I safe?

Only if password logins are off. Using keys yourself does not stop sshd from accepting a password; the bug is exactly that a key-only account becomes reachable with a long password. Set PasswordAuthentication no or update.

### Does Docker on Alpine need a fix?

Only images that run sshd inside the container. A typical Alpine-based image that runs one application and no SSH server is not reachable this way, though you should still rebuild it on a current base.

### Is what I paste uploaded?

No. The check runs in your browser and nothing you paste leaves your device. The account command prints counts, not names or hashes.

Found a problem or have an idea? [Report a problem](https://fbuff.com/contact/?tool=sshole-checker)

Share

## You might also like

- - [PHP2Shell Checker Check if your PHP version is patched against PHP2Shell (CVE-2026-109618, CVE-2026-109619) from php -v or phpinfo() output.](https://fbuff.com/tools/php2shell-checker/)
- - [KSMBD Exposure Checker Paste a few command outputs to see if a Linux server is exposed to the unpatched KSMBD flaws ZDI-CAN-33774 and ZDI-CAN-33549, and turn KSMBD off.](https://fbuff.com/tools/ksmbd-checker/)
- - [CVE-2026-98432 Checker Check if a Linux server has the IPv4 TCP use-after-free CVE-2026-98432 (CVSS 9.8) that Anthropic exploited over MPTCP, and how to patch or harden it.](https://fbuff.com/tools/cve-2026-98432-checker/)
- - [HTTP2Shell Checker Check if Node.js, Bun or Brotli is patched against HTTP2Shell (Node2Shell, CVE-2026-111497) and copy the commands to check, update and block it.](https://fbuff.com/tools/http2shell-checker/)
- - [DarkSword iPhone Check Type your iOS version to see if your iPhone is open to DarkSword or P7 DarkSword spyware, and the update that fixes it.](https://fbuff.com/tools/darksword-check/)
- - [Chrome Zero-Day Check See if your Chrome is patched against the newest zero-day exploited in attacks (CVE-2026-125350), with the safe version numbers and how to update and relaunch.](https://fbuff.com/tools/chrome-zero-day-check/)
- - [Password Generator Generate strong random passwords instantly. 100% client-side.](https://fbuff.com/tools/password-generator/)
- - [2FA Code Generator Generate TOTP codes from your 2FA secret key. Never leaves your browser.](https://fbuff.com/tools/2fa-code/)
- - [MD5 Encoder Generate MD5 hashes from text locally in your browser.](https://fbuff.com/tools/md5-encoder/)
- - [Image Metadata Stripper Remove EXIF, GPS, and all metadata from images locally.](https://fbuff.com/tools/image-metadata-stripper/)
