Resources / Alert

OpenSSH CVE-2026-123158: Who Is Affected by the Password Bypass and How to Check

OpenSSH 10.6p2 closes a password bypass on Linux systems that use musl libc without PAM, such as Alpine Linux. CISA lists it as exploited. Who is affected, who is not, how to check a server, and what an outside check can and cannot see.

On this page · 7 sections
  1. Short answer
  2. How the bypass works, in plain words
  3. How to check a server in a few minutes
  4. What to do
  5. What an outside check shows, and what it cannot
  6. Questions
  7. Sources

In 30 seconds

What happens
A flaw in OpenSSH before 10.6p2 lets an attacker log in without the password on Linux systems that use musl libc without PAM, such as Alpine Linux.
Who it affects
Mainly Alpine Linux servers, virtual machines and devices that run an SSH server with password login switched on.
First step
Find the systems that run Alpine or another musl-based Linux with an SSH server, then update OpenSSH or turn password login off.
Our view
This flaw is narrow, but it sits on SSH, the door administrators use to manage servers. The machines at risk are rarely the main ones: they are small Alpine servers and devices set up once and forgotten. We would start by finding every system that answers on SSH from the internet.

Facts checked on 19 November 2026.

On 5 November 2026, the OpenSSH project released version 10.6p2 with what it calls a critical security workaround for Linux systems that use musl, a small C library some Linux systems use instead of the more common glibc, with PAM, the usual login framework, switched off. On such systems, an attacker who can reach the SSH port can log in to some accounts without knowing the password. The flaw is CVE-2026-123158. On 9 November 2026, CISA, the US cybersecurity agency, added it to its catalog of known exploited vulnerabilities (KEV), its list of flaws with confirmed attacks.

Short answer

  • Who is affected: Linux systems where the SSH server runs with musl libc and without PAM, with OpenSSH before 10.6p2. Alpine Linux is the common case: its standard openssh-server package is built without PAM.
  • Who is not affected (per the published description): distributions built on glibc, such as Ubuntu, Debian and Red Hat Enterprise Linux.
  • Is it attacked: yes. As of 18 November 2026, it is in CISA KEV.
  • What to do: update OpenSSH (on Alpine, the fixed package for your Alpine release) and restart the SSH server. If you cannot update yet, switch password login off.

How the bypass works, in plain words

According to Alpine Linux's advisory of 5 November 2026, the attack needs three things on the same machine: password login switched on, which is OpenSSH's default; an account with no password set, which is normal for accounts that log in only with keys; and at least one other account that does have a password. The attacker then sends a password several hundred characters long and gets into the account that has none. Root itself is protected by OpenSSH's default root login setting unless someone changed it, but any other account that can become root is enough. The CVSS 3.1 score listed on NVD, the US vulnerability database, is 8.1 out of 10.

Alpine names the cases that are not affected: containers that do not run an SSH server, systems with password login switched off, systems using Alpine's openssh-server-pam package with PAM switched on, and cloud images set up with cloud-init, which switches password login off. Alpine adds a warning for its official tiny-cloud images, releases 3.18.11 to 3.24.3: they ship an «alpine» user without a password that can become root without one, so once any account on such a machine has a password, that user can be reached.

How to check a server in a few minutes

Run these three commands on the server:

cat /etc/os-release                            # Alpine, or another system built on musl?
apk list -I 'openssh*'                         # installed OpenSSH packages (Alpine)
sshd -T | grep -iE 'passwordauthentication|usepam'   # run as root

The server is exposed if it runs Alpine, the last command shows "passwordauthentication yes" and "usepam no", and the openssh-server package is older than the fixed version for your Alpine release, for example 10.3_p1-r2 on Alpine 3.24. Do not rely on ssh -V: it shows only the OpenSSH number, which stays the same after Alpine's fix. Alpine 3.21.10, 3.22.8, 3.23.8 and 3.24.4 include the fixed package, and Alpine published fixed packages for older releases back to 3.16.

What to do

  1. Update and restart. On Alpine, install the updates and restart the SSH server; installing the package does not restart a server that is already running.
  2. If you cannot update yet, switch password login off. Set PasswordAuthentication no in the SSH server configuration and restart it. First make sure that logging in with a key works, and keep your current session open until you have tested a new login.
  3. Confirm. The last command below should print "passwordauthentication no" if you switched password login off; after the update, check the package version again.
apk upgrade -U -a
rc-service sshd restart
sshd -T | grep -i passwordauthentication

What an outside check shows, and what it cannot

An outside check shows what is reachable from the internet; it cannot see inside a server. From the internet, anyone can see that a machine answers on the SSH port, usually 22, and often the OpenSSH version it announces. Nobody can see from outside whether that machine uses musl or PAM, or how its accounts are set up. So an outside check tells you which machines to look at; it cannot tell you that one is safe or affected. The machines that matter most here are the ones missing from your list; it helps to compare what you think you expose with what is actually visible.

Questions

  • We run Ubuntu. Does this affect us? By the published description, systems built on glibc, such as Ubuntu, are not in scope. Keep OpenSSH updated anyway, and check whether any container or device in your network runs Alpine with an SSH server.
  • We use Docker containers. According to Alpine, a container that does not run an SSH server is not affected. One that does, built on an Alpine image, needs the fixed package.
  • Can we just block port 22? Limiting who can reach SSH, for example only from your office address or through a VPN, reduces the risk from outside. It does not remove the flaw, so update as well.

Sources

Get started

Know your risks before attackers find them.

Discover your external assets, identify security weaknesses and check for exposed corporate credentials with a free SeguriScan pilot. Get access to the platform, findings and reports to understand what needs attention.

  • Nothing to install
  • No access to your internal network
  • No active testing without your approval

We’ll contact you by email to discuss the pilot and agree on the next steps. No obligation to proceed. What’s included in the pilot →

By submitting this form, you acknowledge that IntruForce will process your personal data to respond to your request. See our Privacy Policy for details.