# SSHole (CVE-2026-123158) is being exploited, but most homelabs aren't affected. Quick way to check yours (Alpine containers are the catch) — retained record

> Retained reddit record from reddit:homelab.

Canonical: https://highsignal.app/data/records/493dea0a589e639f

[← sources](https://highsignal.app/data)


source: [reddit](https://highsignal.app/data/reddit) (reddit:homelab)  published 2026-11-17 18:41 ingested 2026-11-18 02:41

[original source ↗](https://www.reddit.com/r/homelab/comments/1xysi4z/sshole_cve2026123158_is_being_exploited_but_most/)

## retained text



```
Saw a lot of "OpenSSH bug exploited" headlines this week, so here's the short version for homelabs.



Who is affected: sshd built against musl WITHOUT PAM, with password auth on. In practice that means Alpine Linux, including Alpine-based Docker images that run their own sshd. Debian, Ubuntu, Raspberry Pi OS, RHEL and SUSE use glibc + PAM and are not in the affected config.



What attackers are doing (since Nov 7): reading password hashes and root SSH keys, adding their own key to authorized\_keys, querying cloud metadata, dropping a Python remote-access agent and crypto miners. CISA has added it to KEV.



Check:



cat /etc/os-release | head -2

ssh -V

ldd "$(command -v sshd)" | grep -i musl

sudo sshd -T | grep -iE "usepam|passwordauthentication"



Risky combo: musl + usepam no + passwordauthentication yes.



Fix: OpenSSH 10.6p2. On Alpine:



apk update

apk upgrade openssh

rc-service sshd restart



For containers, rebuild from a fresh base image (docker compose build --pull). Can't update yet? Set PasswordAuthentication no and use keys only, and don't expose 22 to the internet.



Also worth a look even if you're not affected: check authorized\_keys for keys you don't recognise.
```



document fetched 2026-11-18 00:40 · canonical https://reddit.com/r/homelab/comments/1xysi4z/sshole_cve2026123158_is_being_exploited_but_most
