Skip to content
Reachability Analysis

CVE-2026-123158: OpenBSD OpenSSH, is it exploitable where you run it

Code called: openReached: yesControl in front: noExploitation known: yesWalk it through the four questions

What the flaw is

When sshd is built without PAM it checks a password by hashing the attempt with crypt() and comparing the result with the stored password field. For an account whose field is too short to hold a salt, such as the * that marks an account with no password, sshd borrows the salt of another account. That code dates from the 2016 fix for CVE-2016-6210.

musl's crypt() returns the one-character string * when it fails, and it fails for any password longer than 256 bytes. The stored field of a no-password account is also *. The two strings match, so the login succeeds. The researcher reports that the bypass also depends on sshd reading its password field from a buffer that libc reuses, so it needs more than one attempt on a connection.

An attacker who can reach the SSH port and knows an account name with a * field logs in without a password. One account with a real SHA-256 or SHA-512 hash makes every no-password account reachable. On Alpine cloud images the alpine user has passwordless doas, so the login becomes root. This page gives no exploit strings.

Are you exposed: each condition and how to check it

Condition for exposureHow to check it on your system
sshd is OpenSSH before 10.6p2 on Linux with musl libc and no PAMRun ssh -V. On Alpine run apk info -v openssh-server and compare it with the fixed package table. A distribution package can carry the fix under an older version string. musl: ldd $(command -v sshd) shows libc.musl (on Alpine, cat /etc/os-release names the distribution). No PAM: ldd $(command -v sshd) | grep -i pam prints nothing, or on Alpine apk info -e openssh-server-pam finds no package, or sshd -T | grep -i usepam shows no.
PasswordAuthentication is yes, the SSH port is reachable, and one account has a * password field while another has a $5$ or $6$ hashPassword authentication: sshd -T | grep -i passwordauthentication shows yes, the default; check Match blocks in /etc/ssh/sshd_config and /etc/ssh/sshd_config.d/ too. A * account: awk -F: '$2=="*"{print $1}' /etc/shadow; also count directory-service users through musl-nscd (nslcd, winbind, sssd), which have no shadow entry, and note that accounts locked with ! are not affected. A hashed account: awk -F: '$2 ~ /^\$[56]\$/{print $1}' /etc/shadow prints names only, and an empty result ends the exposure. Reachable port: ss -ltnp | grep sshd and the firewall and security-group rules for port 22; names such as root or alpine are easy to guess.
Root or an escalation path is available through the * account.Run sshd -T | grep -i permitrootlogin, and check /etc/doas.conf and /etc/doas.d/ for passwordless rules. Alpine tiny-cloud images from 3.18.11 through 3.24.3 ship the alpine user with passwordless doas.

Affected and fixed versions

Alpine's list covers every release back to 3.16. Other musl images (OpenWrt, Buildroot, Yocto) need the 10.6p2 source or the fix commit, which Medcrypt reports applies to OpenSSH 7.3p1 and later.
Product or lineAffectedFirst fixed
OpenSSH portable (Linux, musl, no PAM)Before 10.6p2 (NVD: before 10.6, 10.6, 10.6p1)10.6p2 (5 Nov 2026)
Alpine edgeopenssh before 10.6_p2-r010.6_p2-r0
Alpine 3.24openssh before 10.3_p1-r210.3_p1-r2 (point release 3.24.4)
Alpine 3.23openssh before 10.2_p1-r110.2_p1-r1 (point release 3.23.8)
Alpine 3.22openssh before 10.0_p1-r1110.0_p1-r11 (point release 3.22.8)
Alpine 3.21 (end of support 1 Nov 2026 per the Alpine releases page)openssh before 9.9_p2-r19.9_p2-r1 (point release 3.21.10)
Alpine 3.20openssh before 9.7_p1-r69.7_p1-r6 (package only)
Alpine 3.19openssh before 9.6_p1-r39.6_p1-r3 (package only)
Alpine 3.18openssh before 9.3_p2-r49.3_p2-r4 (package only)
Alpine 3.17openssh before 9.1_p1-r79.1_p1-r7 (package only)
Alpine 3.16openssh before 9.0_p1-r69.0_p1-r6 (package only)
Alpine tiny-cloud images (qcow2, VHD, AMI)3.18.11 through 3.24.3Images from 3.21.10, 3.22.8, 3.23.8 and 3.24.4 and later; older images need an openssh update on each running instance
Linux with glibc, or PAM in the auth path, or non-LinuxNot affected (OpenSSH)Not applicable

If the fix cannot go in yet

  • Upgrade to OpenSSH 10.6p2 or the Alpine fixed package (apk upgrade -U -a), then restart sshd with rc-service sshd restart. Cost: a short sshd restart; existing sessions keep running
  • If you cannot upgrade, set PasswordAuthentication no in sshd_config, including inside Match blocks, check with sshd -t, restart sshd and confirm with sshd -T | grep -i passwordauthentication. OpenSSH and Alpine both give this as the immediate step. Cost: nobody can log in with a password. Test key login in a second session first and keep the first session open
  • OpenSSH's own wording for musl systems without PAM is to set PasswordAuthentication=no or disable SSH immediately. Disabling SSH cuts all remote administration of that host
  • Medcrypt, a third party, reports that MaxAuthTries 1 keeps password login working while blocking its reproduction, and that MaxAuthTries 2 does not. Treat it as a stopgap only. Cost: a user who mistypes a password once is disconnected
  • Images that cannot take 10.6p2: Medcrypt reports the fix commit applies cleanly to OpenSSH 7.3p1 and later. Cost: a rebuild of the image
  • CISA's KEV entry requires applying the vendor mitigations under BOD 26-04, with forensic triage, by 12 Nov 2026

What to look for

  • Alpine: search /var/log/messages for lines reading Accepted password for an account that has no password (alpine, root or any key-only user). Then review doas use, recently created users, new files and authorized_keys entries. If you cannot rule out a login, Alpine says to treat the machine as compromised
  • GreyNoise indicators from intrusions it observed from 7 Nov 2026: scanning and exploitation from 183[.]220[.]91[.]15, 20[.]255[.]63[.]133, 209[.]248[.]50[.]17, 79[.]116[.]138[.]30, 20[.]2[.]81[.]241 and 47[.]80[.]65[.]43; a command-and-control domain tac[.]vpnla[.]org pinned in /etc/hosts as 104[.]21[.]88[.]83; a Python runtime under /opt/py3 unpacked from /tmp/py3.tar.gz; an agent service script at /etc/init.d/tac-agent (SHA-256 7cf69bd6573a90d7bd287810b5c3746841cee6a7f77cadd016f34a97fc7b2361) with files /root/.config/tac/agent.json.lock and /run/tac-agent.pid; and a check for passwordless doas
  • A second GreyNoise cluster (GT12, seen 12 Nov 2026) installs a Python implant and the chisel tunnel tool toward 91[.]149[.]254[.]143 port 853 from 140[.]245[.]33[.]114, and persists with an SSH key and fake tiny-cloud services. GreyNoise says some addresses may be compromised legitimate hosts

Exploited 2 days after disclosure: disclosed 5 Nov 2026, first exploitation reported 7 Nov 2026.

Exploitation reported so far

Exploit code was public on GitHub on 5 Nov 2026, the day of the fix, and GreyNoise saw the first successful exploitation on 7 Nov 2026 at 00:46 UTC. CISA added the flaw to KEV on 9 Nov 2026 and lists ransomware use as unknown. Medcrypt reproduced the bypass on a stock Yocto image on 6 Nov 2026.

GreyNoise tracks the activity on its event page, updated 19 Nov 2026. Its cluster GT10 used the bypass, checked for passwordless doas, installed a Python runtime and an agent that talks to tac[.]vpnla[.]org, and set up a startup service. A second cluster, GT12, installed a Python implant and a tunnel tool. GreyNoise says not all activity belongs to these clusters, and that it cannot see from the network whether a login used the bypass or a real password.

Why static reachability settles it

Exposure rests on build and configuration facts that a read of the package and config settles: musl, no PAM, password authentication on, and a * account next to a hashed account. Those are static properties of the host, so a scan of the build and /etc/shadow gives the answer before any attack arrives, and a severity score or exploit feed cannot say which hosts meet all of them. See static reachability for what the method proves and misses.

Sources

  1. CVE-2026-123158: NVD record, read 19 Nov 2026
  2. CVE-2026-123158: CISA KEV feed (catalog version 2026.11.18), read 19 Nov 2026
  3. CVE-2026-123158: vendor advisory (OpenSSH announcement 'urgent security release: 10.6p2' on openssh-unix-dev), read 19 Nov 2026
  4. CVE-2026-123158: vendor advisory (OpenSSH 10.6p2 release notes), read 19 Nov 2026
  5. CVE-2026-123158: OpenSSH fix commit (GitHub API), read 19 Nov 2026
  6. CVE-2026-123158: distribution advisory (Alpine Linux security advisory), read 19 Nov 2026
  7. CVE-2026-123158: GreyNoise event page and timeline, read 19 Nov 2026
  8. CVE-2026-123158: researcher write-up (Ozgun Kultekin, Wakefield), read 19 Nov 2026
  9. CVE-2026-123158: Medcrypt independent reproduction and mitigation guidance, read 19 Nov 2026
  10. CVE-2026-123158: oss-security thread post by Medcrypt, read 19 Nov 2026
  11. CVE-2026-123158: Alpine Linux releases page (branch end-of-support dates), read 19 Nov 2026

Last reviewed 19 Nov 2026.