OFFSEC · Offensive Security

SSHole: the OpenSSH bypass lives in musl builds, and patched hosts still report the old version

CVE-2026-123158 lets an attacker log in with a password to accounts that are meant to have none. It only affects sshd built with musl and without PAM. It was exploited within days and added to CISA's catalogue four days after release. Version scanning will not tell you whether a host is fixed.

The OpenSSH flaw nicknamed SSHole (also styled *sshole) is narrow in reach and dangerous where it applies. On affected systems, an attacker can authenticate with a password to an account that is supposed to have no password at all [4][12]. Those systems are Linux hosts running sshd built against musl libc without PAM [4][5][7]. Exploitation began within hours of disclosure [13][14][25]. The harder problem for defenders is confirming that a host is fixed. The most common check gives the wrong answer.

What is affected

CVE-2026-123158 covers OpenSSH before 10.6p2 on Linux, built with musl and without PAM [4][5]. The weakness is classed as CWE-394, an unexpected status code or return value [4][5]. In one line: musl’s crypt() returns a failure marker that matches the shadow field of a password-disabled account, so a failed hash is treated as a match [4][12][23]. OpenSSH says the root cause lies outside sshd but can be avoided there [1][2]. The musl maintainer, Rich Felker, says it is not a musl bug but caller misuse. He adds that musl will very likely change the behaviour in its next release cycle [3]. The researcher credited with the discovery is Özgün Kültekin of Wakefield [1][2][12].

Alpine’s advisory sets out the conditions [7]. The server must be built without PAM, or be the PAM build with UsePAM disabled. Password authentication must be enabled, which is the default [12][25]. The target account’s password field must be exactly an asterisk. That is how root is locked on recent images, and how key-only users are often set up. At least one local account must have a SHA-256 or SHA-512 crypt hash. Accounts locked with an exclamation mark are not affected [26]. To reach root, PermitRootLogin must also allow it [27].

Alpine branches 3.21 to 3.24 and edge are affected, as are unsupported 3.16 to 3.20 [7][24]. The exposure goes well beyond Alpine servers. OpenWrt devices that use OpenSSH instead of Dropbear are in scope, as are Buildroot and Yocto builds using musl and the container images derived from them [12][24][25][27]. Medcrypt reproduced the bug on a stock Yocto image with no unusual configuration [15]. That matters for embedded and medical devices, which are rarely patched quickly. glibc builds are not affected (Debian, Ubuntu, Fedora, RHEL), and neither are PAM-enabled builds, Dropbear or OpenBSD [12][23][25][26].

The vendor record is inconsistent

Ubuntu rates the CVE high priority with CVSS 8.1. It marks every release from 14.04 to 26.10 not affected, because its OpenSSH is linked against glibc and uses PAM [9]. Red Hat also says its products are not affected, but publishes a preliminary score of 9.8 [10]. SUSE rates it important and marks every product not affected [11]. The Debian tracker shows the fix in forky and sid. It lists bookworm and trixie as vulnerable without explanation [8]. Teams that act on tracker status alone could spend effort on glibc hosts that are not at risk. The MITRE score of 8.1 assumes high attack complexity. Red Hat’s 9.8 assumes low [4][5][10]. CISA supplied no CVSS score. Its SSVC assessment records exploitation as active and technical impact as total [4][5].

Timeline and exploitation

The fix was committed late on 4 November, and Portable OpenSSH 10.6p2 shipped on 5 November [1][2][13]. Alpine published its advisory and packages the same day [7]. GreyNoise records a public proof-of-concept on GitHub that afternoon. The CVE record was published at 15:46 UTC [4][13]. CISA added the flaw to the KEV catalogue on 9 November, with a federal remediation deadline of 12 November [5][6][21][22].

Accounts of first exploitation differ. Previdian reported a first attempt within nine hours of publication and root access on an Alpine honeypot [25]. GreyNoise records its first successful in-the-wild exploitation at 00:46 UTC on 7 November [13]. SANS Internet Storm Center saw long-password attempts rise from 58 on 4 November to 713 on 6 November, then fall to 51 by 8 November [14]. Counts of attackers grow with each snapshot. Previdian reported 8 attempts from one address, then 20 from 13, then 22 from 14 [20][21][25]. watchTowr reported botnet and cryptomining activity [20][21].

Observed post-exploitation activity includes cloud-metadata queries and attempts to read the shadow file and root’s SSH keys. Attackers also added SSH keys and started a second sshd on a high port. GreyNoise documents one cluster installing a Python agent as a persistent service [13][20][21]. None of the cited sources names a victim outside honeypots or reports ransomware use.

Why version checks fail

Alpine fixed every supported branch by patching the existing package, not by moving to 10.6p2. On 3.24, for example, the fixed package is 10.3_p1-r2 [7][27]. StepSecurity found that sshd -V on a patched host still printed the old version string [27]. CyCognito noted that a version banner cannot tell a musl build from a glibc build. Its active tests found no exploitable assets [26]. No scanner has published a count of vulnerable hosts. The large SSH exposure figures in circulation count every host with port 22 open [20][24].

Regional coverage is thin. HKCERT issued a high-risk bulletin on 6 November [16]. As of 19 November, CSA Singapore, JPCERT/CC and NACSA had published no alert for this CVE [17][18][19]. Sensor data list source addresses in Japan, Singapore, Hong Kong, South Korea, Taiwan and Australia [13][20]. Those are attack origins, not victims.

What to do

  • Inventory by build, not banner. Identify sshd binaries linked against musl across servers, containers, appliances and firmware. Check the installed package version (apk info -v openssh-server on Alpine) [7][27].
  • Upgrade and restart. Installing the fixed package does not replace the running daemon [7][24][25].
  • If you cannot upgrade, disable password authentication after confirming key access works, or use the PAM build with UsePAM enabled [3][7][27].
  • Rebuild container images on a patched base image. Do not patch running containers in place [27].
  • Hunt. Look for accepted password logins to accounts that have no password, such as root, alpine or key-only users. Look for long password attempts, changes to authorized_keys, and new services or listeners. Where a login cannot be ruled out, treat the host as compromised [7][14][25].
  • Restrict TCP/22 to management networks or a bastion host, and audit the shadow file for bare-asterisk password fields [12][26].

SSHole is a failure where two components meet: an error value one library uses and another misreads. Defenders who rely on vendor version strings and distribution trackers will get wrong answers on both sides, false alarms on glibc hosts and false comfort on patched-looking musl ones. Assess this bug by checking how each sshd binary was built.

Sources

Every R3KONX article cites its primary material. 27 sources, in order of first citation. Links open the original publication.

  1. OpenSSH Release Notes: OpenSSH 10.6p2 OpenSSH project · 2026-11-05
  2. Announce: Portable OpenSSH 10.6p2 released oss-security (Openwall) · 2026-11-05
  3. Advisory for OpenSSH+musl users musl mailing list (Openwall) · 2026-11-05
  4. CVE-2026-123158 record CVE Program (MITRE CNA, CISA ADP) · 2026-11-10
  5. CVE-2026-123158 NIST National Vulnerability Database · 2026-11-10
  6. CISA Adds Four Known Exploited Vulnerabilities to Catalog CISA (GovDelivery bulletin) · 2026-11-09
  7. OpenSSH password authentication bypass Alpine Linux · 2026-11-05
  8. CVE-2026-123158 Debian Security Tracker · 2026-11-19
  9. CVE-2026-123158 Canonical Ubuntu · 2026-11-18
  10. CVE-2026-123158 Red Hat · 2026-11
  11. CVE-2026-123158 SUSE · 2026-11-14
  12. *sshole: OpenSSH password authentication bypass on musl Özgün Kültekin (Wakefield) · 2026-11
  13. SSHole events tracker GreyNoise · 2026-11-18
  14. Scans for Sshole Vulnerability (CVE-2026-123158) SANS Internet Storm Center · 2026-11-08
  15. Re: sshole: password authentication bypass: OpenSSH + musl libc oss-security (Medcrypt) · 2026-11-09
  16. OpenSSH Security Restriction Bypass Vulnerability HKCERT · 2026-11-10
  17. Alerts and advisories Cyber Security Agency of Singapore · 2026-11-19
  18. 注意喚起 2026 JPCERT/CC · 2026-11-19
  19. NC4 alerts and advisories National Cyber Security Agency (NACSA) Malaysia · 2026-11-19
  20. Hackers exploit SSHole OpenSSH flaw to breach Linux systems BleepingComputer · 2026-11-09
  21. CISA Warns of Active Exploitation of OpenSSH, GPUStack, FreeSWITCH, and IBM Flaws The Hacker News · 2026-11-10
  22. CISA Adds Four Exploited Flaws to KEV, Sets Nov. 12 Patch Deadline eSecurityPlanet · 2026-11-10
  23. OpenSSH flaw lets attackers access password-disabled accounts on some Linux systems CSO Online · 2026-11-05
  24. OpenSSH rushes patches for SSHole authentication bypass SecurityWeek · 2026-11-06
  25. OpenSSH flaw exploited in the wild just hours after disclosure Help Net Security · 2026-11-06
  26. Emerging Threat: CVE-2026-123158 OpenSSH password authentication bypass on musl Linux CyCognito · 2026-11-09
  27. CVE-2026-123158: sshhole OpenSSH musl password bypass StepSecurity · 2026-11-06

Researched and written by the R3KONX Analysis Desk from the cited primary material. Exploitation figures are snapshots from honeypot and sensor networks taken on different dates and are not directly comparable. The CISA catalogue entry is cited through CISA's bulletin and NVD because cisa.gov could not be retrieved. Corrections: event@r3konx.asia.

R3KONX 2027

Work in this domain? So does the programme

4–6 May 2027, World Trade Centre Kuala Lumpur. Curated talks, hands-on training and The BattleGrid.