The OpenSSH password bypass, tracked as CVE-2026-123158, lets an attacker log in to locked accounts by sending a password longer than 256 characters. First, it affects OpenSSH on musl based Linux systems, including Alpine, that run without PAM. Then OpenSSH 10.6p2, released November 5, 2026, closes the gap. Therefore, update and restart sshd now.
What Is the OpenSSH Password Bypass CVE-2026-123158?
CVE-2026-123158 is the OpenSSH password bypass nicknamed sshole, a password authentication flaw in the OpenSSH server. Özgün Kültekin of Wakefield reported it, and the OpenSSH project credits him in the release notes. In short, an attacker who knows the name of an account with password login disabled can still get in. Because the attacker needs no valid password for that account, the flaw turns a locked account into an open door.
The OpenSSH developers say the root cause sits outside sshd. Nevertheless, sshd is the program that exposes it, so the OpenSSH team changed sshd to avoid the problem. Their OpenSSH 10.6p2 release notes describe the change.
How Does the OpenSSH Password Bypass Work?
The OpenSSH password bypass depends on one detail. Locked accounts store an asterisk (*) in the password field, which means no password can ever match. Normally, sshd hashes the password you type and compares the result to that stored value. However, the musl C library caps passwords at 256 bytes, and its crypt function returns an asterisk when the input is too long. As a result, the result of an oversized password matches the asterisk stored for the locked account, and sshd accepts the login.
In testing, passwords between 257 and 1,024 characters triggered the bypass. Specifically, the attacker needs only a reachable SSH port, the name of a password disabled account and a long string.
Which Systems Does the OpenSSH Password Bypass Affect?
A system carries the OpenSSH password bypass risk only when every condition below is true. For that reason, most Linux servers are safe, but default Alpine installations are not.
Alpine Linux meets all of them in its default openssh-server setup, and the bug hits the official Alpine cloud images from version 3.18.11 through 3.24.3. Moreover, the default alpine account has pass-wordless doas rights, so an attacker who logs in as that account can become root. Embedded distributions that use musl may also carry the risk.
On the other hand, the bug does not touch systems built on glibc, such as Debian, Ubuntu and Fedora. Likewise, PAM based setups, the Dropbear SSH server and OpenBSD stay safe. Red Hat confirms in its CVE record for CVE-2026-123158 that its products use glibc and PAM, so they do not meet the conditions.
To check your own system, run these two commands. The first shows the C library, and the second shows the OpenSSH version.
What Do the Scores Say About the OpenSSH Password Bypass?
Here is the evidence for the OpenSSH password bypass at a glance. Each value comes from the vendor and project records listed.
| Item | Value |
|---|---|
| CVE ID | CVE-2026-123158 |
| CVSS v3.1 base score | 8.1 (High) |
| CVSS vector | AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H |
| Weakness (CWE) | CWE-303, incorrect implementation of an authentication algorithm |
| Fixed version | OpenSSH 10.6p2, released November 5, 2026 |
| Affected conditions | musl libc, OpenSSH built without PAM, password login enabled |
| Public proof of concept | Yes, unverified and possibly unsafe |
| CISA KEV status | Not listed as of November 6, 2026 |
| NVD score | Not yet provided at the time of writing |
The vector explains the 8.1 rating. The attack works over the network with no privileges and no user interaction, and it gives full control of the account. However, CVSS rates the complexity as high, because the attacker needs the right account setup on the target. As a result, the score lands in the High range and not in Critical. Still, a default Alpine server meets every condition, so treat it as urgent. Check the National Vulnerability Database entry for updates to the score.
Is Anyone Exploiting the OpenSSH Password Bypass?
Yes, according to one report. A threat intelligence firm said its sensors saw attacks on this flaw less than nine hours after the CVE went public, and at least one attack succeeded against a honeypot that ran Alpine and OpenSSH. The firm counted eight attempts from a single IP address in Japan. In those attempts, the attacker sent oversized passwords and then ran reconnaissance commands such as id, uname and hostname.
Meanwhile, public proof of concept exploits exist on GitHub. Be careful, however, because nobody has verified them and they could contain malware. As of November 6, 2026, CISA had not listed the flaw in its Known Exploited Vulnerabilities catalog. Because that status can change, check the catalog before you finalize your risk rating.
How Strong Is the Evidence Behind the OpenSSH Password Bypass?
We separate confirmed facts about the flaw from single reports, so you can judge the risk yourself.
- Confirmed by the OpenSSH project: the bypass exists on musl systems without PAM, the root cause lies outside sshd, and version 10.6p2 avoids it
- Confirmed by the CVE record: the CVSS 8.1 score, the vector, the CWE and Red Hat’s statement that its products are not affected
- Reported by one firm: the in the wild attempts, the Japan based source address and the honeypot compromise
- Still open: an NVD score, a CISA KEV decision and the full list of embedded distributions that use musl
How Do You Check Whether Attackers Used the OpenSSH Password Bypass?
First, look for the trace this flaw leaves behind, which is a successful password login on an account that should never accept one. On Alpine, these entries appear in the system log:
Next, review every account the attacker could have used. In particular, check for logins by root, by key only users and by the default alpine account. Then look for new users, changes to authorized_keys files and recent doas activity. If you cannot rule out a login, treat the server as compromised and rebuild it from a known good image.
How Do You Fix the OpenSSH Password Bypass?
Fixing the flaw takes five steps, and the order matters.
- Update OpenSSH to version 10.6p2 or to your distribution’s patched package
- Restart sshd, because an update alone leaves the old process running
- Confirm the new version with ssh -V
- If you cannot update, set PasswordAuthentication no and use key based login only
- Rotate credentials and review authorized_keys on any server you cannot clear
On Alpine, these commands update the package and restart the service. Run them as root, and confirm the package name for your release first.
If you must wait for a patch, add this line to /etc/ssh/sshd_config and restart sshd. Note that it turns off password login completely.
What Should Security Teams Do After the OpenSSH Password Bypass?
Above all, find every musl based host that could carry this flaw, including container images and embedded devices, because teams rarely track them. For example, our team runs penetration testing and vulnerability assessments that show which of your SSH servers an attacker can really reach. In addition, our PTaaS platform keeps that testing running between audits. Finally, our 2026 Mid Year Threat Pattern Report explains how quickly attackers turn a new disclosure into live attacks.
Key Takeaways
- The OpenSSH password bypass, CVE-2026-123158, lets a password longer than 256 characters unlock locked accounts on musl based Linux without PAM
- The CVSS v3.1 score is 8.1 High, and default Alpine installations meet every condition
- OpenSSH 10.6p2 fixes it, and you must restart sshd after the update
- One firm reports in the wild attempts within nine hours, and CISA had not listed the flaw as of November 6, 2026
- Check logs for accepted password logins on accounts that should have no password
Frequently Asked Questions About the OpenSSH Password Bypass
What is the OpenSSH password bypass CVE-2026-123158?
It is a flaw that lets an attacker log in to an SSH account that has password login disabled, simply by sending a very long password. It affects OpenSSH servers on musl based Linux systems, such as Alpine, when OpenSSH runs without PAM.
Which OpenSSH version fixes CVE-2026-123158?
OpenSSH 10.6p2, released on November 5, 2026, fixes the OpenSSH password bypass. However, you must also restart sshd after you update, because the old process keeps running until you do.
Is Ubuntu, Debian or Red Hat Linux affected by the OpenSSH password bypass?
No. Those systems use glibc and PAM by default, so the conditions for the bug do not exist. In fact, Red Hat states that the bug does not touch any of its products.
What is the CVSS score for CVE-2026-123158?
The OpenSSH password bypass carries a CVSS v3.1 base score of 8.1, which is High. The vector is AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H, and the complexity rating is high because the attacker needs the right account setup on the target.
Are attackers exploiting CVE-2026-123158?
One threat intelligence firm reported attempts to use the OpenSSH password bypass less than nine hours after the CVE went public, and at least one succeeded against an Alpine honeypot. Public proof of concept exploits also exist. As of November 6, 2026, CISA had not added the flaw to its KEV catalog.
How can I protect my servers right now?
To close the OpenSSH password bypass, first update OpenSSH to 10.6p2 and restart sshd. If you cannot update yet, set PasswordAuthentication no in your sshd configuration. Then search your logs for accepted password logins on accounts that should have no password.

