Skip to main content
Season 3 ends in 25 d 11:42:29 $2,000 10,000 pts = 1 month Premium
Online Security

OpenSSH Vulnerability 2026: SSHole Login Bypass and Fix

Published 14 min read
Open the post and read it to claim 30 points
A closed padlock on a server rack with a long gold ribbon trailing along the floor, symbolising SSHole's long-password bypass

Sign in and earn +30 points by reading this

Read to the end, wait a few seconds, then tap the claim button below.

In short

The OpenSSH vulnerability CVE-2026-123158, nicknamed SSHole, lets attackers log in without a password on Linux systems that use musl libc without PAM, such as Alpine [1][2]. OpenSSH 10.6p2 fixed it on 5 November 2026 [1]; CISA listed it as exploited on 9 November [3]. Update and restart sshd now.

Key takeaways

  1. CVE-2026-123158 is a password authentication bypass in sshd that only works on Linux with musl libc and PAM disabled [1][4].
  2. Alpine Linux is the main affected platform; OpenWrt, Buildroot and Yocto builds can be affected if OpenSSH runs without PAM [2][6][8].
  3. Red Hat says its products, which use glibc and PAM, are not affected, and Debian's tracker describes the bug as limited to Linux with musl libc and no PAM [4][5].
  4. The fix is OpenSSH 10.6p2 (5 November 2026) or the patched Alpine package for your branch, followed by an sshd restart [1][2].
  5. CISA added the flaw to its Known Exploited Vulnerabilities catalog on 9 November 2026 with a 12 November deadline for US federal agencies, which has now passed [3].
  6. If you cannot update, setting PasswordAuthentication no closes the hole [2].
On this page 14 sections
  1. What is the SSHole OpenSSH vulnerability?
  2. How does the SSHole login bypass work?
  3. Am I affected by CVE-2026-123158?
  4. Which versions fix the OpenSSH vulnerability?
  5. How do I fix SSHole on Alpine Linux?
  6. What if I cannot update OpenSSH yet?
  7. Is SSHole being exploited in attacks?
  8. How can I tell if my server was hacked through SSHole?
  9. Why do severity scores for SSHole differ?
  10. What else should SSH server owners do now?
  11. Common mistakes
  12. Frequently asked questions
  13. Glossary
  14. Sources

What is the SSHole OpenSSH vulnerability?

SSHole is the nickname for CVE-2026-123158, a flaw that lets a remote attacker log in to some accounts on an SSH server without knowing any password [2][6]. It affects the OpenSSH server, sshd, only when it runs on Linux with the musl C library and without PAM, the Pluggable Authentication Modules framework [1][4].

The OpenSSH team shipped a workaround in Portable OpenSSH 10.6p2 on 5 November 2026 and described it as a critical security workaround for Linux systems that use musl libc with PAM disabled [1]. The project said it considers the root cause to lie outside sshd, but that the bug is exploitable through sshd and can be avoided there [1]. Alpine Linux published its own advisory and fixed packages the same day [2].

The bug was reported by Özgün Kültekin of Wakefield [1][2]. Alpine's advisory sums up the risk bluntly: an attacker who can reach the SSH port can log in in one connection, every time, with no retries [2].

How does the SSHole login bypass work?

The bypass works because musl's password-hashing function returns a single asterisk on error, and an asterisk is exactly what the password field holds for accounts that have no password [2].

When sshd is built without PAM, it checks a password by hashing the attempt with the C library function crypt() and comparing the result with the stored password field in /etc/shadow [2]. For an account whose stored field is too short to contain a salt, such as a key-only account with *, sshd borrows the salt of another account on the machine [2][6].

musl's crypt() fails when the key is longer than 256 bytes and returns * as its error value instead of NULL [2][6]. Because that matches the stored *, sshd treats the password as correct [2]. An attacker therefore only needs to send a very long password, between 257 and 1024 bytes according to Alpine, for a passwordless account [2]. The CVE record describes the range as 256 to 1024 characters [5].

Two conditions make the trick work: an account whose password field is *, and at least one other local account with a SHA-256 ($5$) or SHA-512 ($6$) password hash whose salt can be borrowed [2]. One user with a password is enough to make every passwordless account reachable [2].

A brass balance scale with an identical gold asterisk token in each pan, illustrating how the OpenSSH check matches an asterisk with an asterisk
musl returns an asterisk on error, and a passwordless account stores an asterisk, so the two match.

Am I affected by CVE-2026-123158?

You are affected only if all four conditions below are true at the same time, according to Alpine's advisory [2].

  • You run Alpine's openssh-server package, which is built without PAM, or openssh-server-pam with UsePAM no [2].
  • PasswordAuthentication is set to yes, which is the OpenSSH default [2].
  • The machine has an account whose password field is *, such as root (shipped as root:* since about Alpine 3.16), key-only users created with adduser, directory users through musl-nscd, or the alpine user in tiny-cloud images [2].
  • At least one local account has a $5$ or $6$ password hash [2].

Root has some extra protection: OpenSSH's default PermitRootLogin prohibit-password blocks password logins for root, but that does not help if another reachable account can become root, for example through doas [2].

Outside Alpine, SecurityWeek and the French health-sector CERT list other musl-based systems such as OpenWrt, Buildroot and Yocto, but only when OpenSSH's server is installed without PAM [6][8]. Routers and embedded devices that use the Dropbear SSH server instead of OpenSSH are not affected by this specific bug [8].

Red Hat says none of its products are affected because they link OpenSSH against glibc and use PAM by default [4]. Debian's tracker describes the bug as limited to Linux with musl libc and no PAM and shows urgency "unimportant" for the fixed unstable entry; its table still marks the bookworm and trixie package versions as "vulnerable" by version number [5]. Ubuntu is not covered by any source checked here.

A home Wi-Fi router, a small embedded circuit board and a slim rack server with red-glowing network ports, showing devices that may run OpenSSH on musl
Alpine servers and some embedded Linux devices can be affected; Dropbear-based devices are not.

Which versions fix the OpenSSH vulnerability?

Upstream, the fix is Portable OpenSSH 10.6p2, released on 5 November 2026; on Alpine, each branch has its own patched package [1][2]. Alpine 3.21.10, 3.22.8, 3.23.8 and 3.24.4 already contain the fixed package, and Alpine also published fixes for releases that no longer get regular updates, back to 3.16 [2].

The upstream commit "avoid password authn bypass" adds a check that the stored hash is at least four characters long before the comparison [10]. Debian's unstable branches (forky and sid) carry 1:10.6p2-1 [5]. If you build OpenSSH yourself for firmware or containers, you need 10.6p2 or later [1].

The table below lists the fixed Alpine package for each branch.

How do I fix SSHole on Alpine Linux?

Update the openssh package and restart sshd; the upgrade alone does not replace the daemon that is already running [2].

  1. Run apk upgrade -U -a as root to install the fixed package for your branch [2][8].
  2. Restart the server with rc-service sshd restart [2].
  3. Check the installed openssh-server package version and compare it with the fixed versions in the table above [2].
  4. Repeat on every running cloud instance. Alpine warns that tiny-cloud images from 3.18.11 through 3.24.3 are safe on first boot but become exploitable as soon as any $6$ hash exists, for example after an admin sets a console password [2].
  5. Use patched images for new deployments: Alpine lists tiny-cloud images built from 3.21.10, 3.22.8, 3.23.8, 3.24.4 and later as fixed [2][8]. Rebuild container and firmware images that bundle sshd as well, so they do not reintroduce the old package.

Keep an existing SSH session open while you restart, so a configuration error does not lock you out [2].

What if I cannot update OpenSSH yet?

Turn off password logins: setting PasswordAuthentication no and restarting sshd closes the hole on its own [2]. First make sure your SSH key login works, and keep your current session open until a new login succeeds [2].

  1. Create a drop-in file: mkdir -p /etc/ssh/sshd_config.d and write PasswordAuthentication no into /etc/ssh/sshd_config.d/00-no-passwords.conf. Alpine's default configuration reads that folder from 3.19 onward [2].
  2. On older releases, change every PasswordAuthentication line in /etc/ssh/sshd_config, including lines inside Match blocks [2][8].
  3. Check and restart: sshd -t && rc-service sshd restart [2].
  4. Verify: sshd -T | grep -i passwordauthentication should print passwordauthentication no [2].

Other options are switching to openssh-server-pam with UsePAM yes, or turning SSH off on machines that do not need it [2][8]. SecurityWeek also notes that disabling SSH entirely is a valid stopgap [6].

A metal toggle switch beside a USB security key, showing how disabling password logins blocks the OpenSSH bypass
Turning off password logins blocks SSHole even before the patch is installed.

Is SSHole being exploited in attacks?

Yes. CISA added CVE-2026-123158 to its Known Exploited Vulnerabilities catalog on 9 November 2026, which means it has evidence of active exploitation [3]. The agency gave US federal civilian agencies only until 12 November to fix it and marked forensic triage as required under CISA's BOD 26-04 [3]. That deadline has now passed.

Security firms reported attacks within days of disclosure. Previdian said its sensors saw 20 exploitation attempts from 13 attacker IP addresses in nine countries between 6 and 8 November [6]. watchTowr said the early activity came from botnets and cryptocurrency miners [6].

GreyNoise reported that a cluster it tracks as GT10 successfully exploited its sensors in countries including New Zealand, Laos, Australia, India, Japan, Hong Kong, South Korea, Taiwan and France, and that its command logs show Python 3 being installed with apk add --no-cache python3 and a Python implant called TAC Agent being deployed [9]. According to GreyNoise, TAC Agent can run shell commands and transfer files, has no built-in persistence, and in the two intrusions described its command server did not hand it any task; at least one intruder added a startup service for it [9]. Ars Technica also reported on the GreyNoise findings [7]. These are claims by individual security vendors and have not been independently confirmed beyond their reports [6][9].

Exploitation is cheap for attackers. Alpine says the attack takes one connection and works every time, and CERT Santé says a public proof of concept exists [2][8].

How can I tell if my server was hacked through SSHole?

Look in /var/log/messages for sshd lines reading "Accepted password for" an account that has no password, such as alpine, root or a key-only user [2]. On a vulnerable system those accounts should never log in with a password, so any such line is a red flag.

  • Review doas use and recently created users, files and authorized_keys entries on exposed machines [2].
  • Look for unexpected Python 3 installations and unknown long-running processes, which match what GreyNoise reported from the GT10 campaign, including a Python runtime unpacked under /opt/py3 and an init script named tac-agent [9].
  • Watch for new cron jobs, high CPU use from crypto miners and outbound connections to unknown hosts, given watchTowr's reports of miner activity [6].

Alpine's guidance is clear: if you cannot rule out a login, treat the machine as compromised [2]. That usually means rebuilding it from a known-good image, rotating SSH keys and any secrets stored on it, and reviewing other machines it could reach.

Why do severity scores for SSHole differ?

Red Hat scores CVE-2026-123158 at 9.8 out of 10, while the score in the CVE record is 8.1, because they disagree on how hard the attack is [4]. Red Hat rates attack complexity as low; the CVE record rates it as high [4]. Red Hat labels its scores preliminary [4].

Both views are reasonable. On a default glibc server the bug does not apply at all [4][5]. On a matching Alpine machine, Alpine says it works on the first try [2]. Red Hat says its products are not affected and Debian lists urgency "unimportant" for the fixed unstable entry, while CISA lists the flaw as actively exploited [3][4][5].

For practical decisions, the CVSS number matters less than one question: does any of your machines run OpenSSH on musl without PAM and with password logins enabled [2]? If yes, treat it as urgent.

What else should SSH server owners do now?

Use SSH keys instead of passwords wherever possible, keep sshd updated, and expose SSH to the internet only where it is really needed [2][6]. Key-only logins with PasswordAuthentication no would have blocked SSHole even before the patch [2].

The OpenSSH team says it will make more frequent releases so bugfixes reach users sooner, and it notes that adversaries who do not report bugs may find the same ones [1]. Expect more frequent OpenSSH releases and plan for quick updates.

Limit SSH to a VPN or allow-listed addresses, and keep logs long enough to investigate incidents. For a recent server-side Linux flaw, the Pouyam guide CVE-2026-98432 Explained: The Linux TCP Flaw and How to Protect Your Servers covers patching steps. To move people off passwords, see What Are Passkeys? How Passwordless Sign-In Works and Why It Is Safer and Two-Factor Authentication Explained: Which 2FA Method Is Safest?

Who is and is not affected by CVE-2026-123158 (Alpine and Red Hat advisories)
SetupAffected?Source
Alpine openssh-server (no PAM), passwords on, a * account plus a $5$/$6$ hashYesAlpine [2]
Alpine openssh-server-pam with UsePAM noYesAlpine [2]
Alpine openssh-server-pam with UsePAM yesNoAlpine [2]
Any system with PasswordAuthentication noNoAlpine [2]
Containers that do not run sshdNoAlpine [2]
Red Hat Enterprise Linux and other Red Hat products (glibc and PAM by default)NoRed Hat [4]
OpenWrt, Buildroot, Yocto with OpenSSH and no PAMPossiblyCERT Santé [8]
Devices using Dropbear instead of OpenSSHNoCERT Santé [8]
Fixed openssh package by Alpine branch (Alpine advisory, 5 November 2026)
Alpine branchFixed openssh versionNotes (Alpine advisory)
edge10.6_p2-r0Fixed package published
3.2410.3_p1-r2Fixed in image 3.24.4
3.2310.2_p1-r1Fixed in image 3.23.8
3.2210.0_p1-r11Fixed in image 3.22.8
3.219.9_p2-r1Fixed in image 3.21.10; end of support since 1 Nov 2026
3.209.7_p1-r6No longer receives regular updates; fixed package published
3.199.6_p1-r3No longer receives regular updates; fixed package published
3.189.3_p2-r4No longer receives regular updates; fixed package published
3.179.1_p1-r7No longer receives regular updates; fixed package published
3.169.0_p1-r6No longer receives regular updates; fixed package published

Common mistakes

  • Upgrading the package but not restarting sshd.

    Fix: Run rc-service sshd restart; the old daemon keeps running until you do [2].

  • Assuming root is safe so the server is safe.

    Fix: Any passwordless account, such as alpine with doas, can be the way in [2].

  • Disabling password logins without testing key access.

    Fix: Test a key login and keep a session open before restarting [2].

  • Patching running servers but not images.

    Fix: Use patched images and rebuild container, cloud and firmware images that bundle sshd [2][8].

  • Panicking on Red Hat or Debian servers.

    Fix: Red Hat says its products are not affected, and Debian's tracker limits the bug to musl without PAM [4][5].

Frequently asked questions

What is the SSHole OpenSSH vulnerability?

CVE-2026-123158, a password bypass in sshd on Linux systems using musl libc without PAM, such as Alpine [1][2].

Am I affected by CVE-2026-123158?

Only if you run OpenSSH on musl without PAM, allow password logins, and have both a * account and a $5$/$6$ hashed account [2].

Which versions fix the OpenSSH vulnerability?

OpenSSH 10.6p2, or Alpine's patched packages such as 10.3_p1-r2 on 3.24 [1][2].

How do I fix SSHole on Alpine Linux?

Run apk upgrade -U -a, then rc-service sshd restart [2].

Is SSHole being exploited in attacks?

Yes. CISA listed it as exploited on 9 November 2026, and several security firms reported attacks [3][6][9].

Are Debian and Red Hat servers affected?

Red Hat says its products are not affected, and Debian's tracker describes the bug as limited to Linux with musl libc and no PAM [4][5].

Glossary

sshd
The OpenSSH server program that accepts remote SSH logins [1].
musl libc
A C standard library used by Alpine Linux and some embedded Linux builds such as OpenWrt, Buildroot and Yocto [6].
PAM
Pluggable Authentication Modules, a Linux framework that handles login checks [4].
crypt()
The C library function that turns a password into its stored hash [2].
KEV catalog
CISA's list of vulnerabilities with evidence of active exploitation [3].

Sources

  1. OpenSSH Release Notes: OpenSSH 10.6p2 OpenSSH · 2026-11-05
  2. Security advisory: openssh-server password authentication bypass Alpine Linux · 2026-11-05
  3. Known Exploited Vulnerabilities Catalog: CVE-2026-123158 CISA · 2026-11-09
  4. CVE-2026-123158 Red Hat Customer Portal
  5. CVE-2026-123158 Debian Security Tracker
  6. Hackers Exploiting 'SSHole' Authentication Bypass in OpenSSH SecurityWeek · 2026-11-09
  7. Vulnerability that lets hackers SSH into Linux devices is under active exploitation Ars Technica · 2026-11-09
  8. OpenSSH - CVE-2026-123158 CERT Santé (ANS) · 2026-11-06
  9. SSHole (CVE-2026-123158) Activity 2026 GreyNoise
  10. avoid password authn bypass OpenSSH Portable (GitHub)
Share this guide Telegram WhatsApp X
0 likes

Comments

Top comments

About the Pouyam Team Editorial policy

On Pouyam

Explore Pouyam

Guides are one corner of Pouyam. Here is where to go next.

Quick navigation