The OpenSSH team released portable OpenSSH 10.6p2 on November 5, 2026, to prevent the bypass in sshd. Alpine Linux also shipped patched packages for its maintained and older branches.The issue does not make every OpenSSH server vulnerable. A reachable server also needs password authentication enabled and a particular mix of account password fields. Check the running service and its configuration before classifying a host as exposed.
What it allows
How Does CVE-2026-123158 Bypass OpenSSH Password Checks?
Alpine Linux explains that a PAM-free sshd compares a computed password hash with a stored account password field. Under the affected conditions, musl returns an error marker that matches a placeholder in a passwordless account. OpenSSH describes the root cause as outside sshd, but says the bypass is reachable through sshd.
An attacker who knows a qualifying account name and can reach the SSH service may authenticate as that account without its password. Alpine says a separate local account with a compatible password hash must also exist. Its advisory distinguishes this combination from key-only accounts alone. For teams tracking the affected hosts and fix evidence, the vulnerability intelligence platform is the relevant Brandefense product page.
CISA listed CVE-2026-123158 in KEV on November 9, 2026. That listing is evidence of exploitation, but it does not identify a victim or establish a specific campaign here.
Brandefense Blackhole counted 30 dark chat posts matching the CVE from August 16 through November 14, 2026. This is a discussion count, not a count of intrusions. A GitHub repository search returned 41 results for the CVE query on November 13, 2026; search results do not verify exploitation.
Who is affected
Which OpenSSH Hosts Are Affected by CVE-2026-123158?
The OpenSSH 10.6p2 release notes identify Linux systems using musl libc with PAM disabled. Alpine narrows the practical exposure to hosts running sshd with password authentication enabled. Its advisory also requires a login-eligible account with * in its password field and at least one local account with a $5$ or $6$ password hash. An internet-facing SSH port increases reachability, but the configuration and account conditions still determine exposure.
Alpine says its standard openssh-server package is built without PAM. The openssh-server-pam variant is affected when UsePAM is set to no, and Alpine says UsePAM yes avoids this issue. It also lists password authentication disabled as outside the affected configuration. Do not infer exposure from an OpenSSH banner or an Alpine release number alone.
Portable OpenSSH 10.6p2 contains the upstream workaround. Alpine backported its fix into branch packages, so a lower upstream version number can still be patched.
Alpine lists fixed openssh packages as 10.6_p2-r0 for edge; 10.3_p1-r2 for 3.24; 10.2_p1-r1 for 3.23; 10.0_p1-r11 for 3.22; and 9.9_p2-r1 for 3.21. The advisory also lists fixed packages for older 3.16 through 3.20 branches. Verify the exact package release against the appropriate Alpine branch.
For the initial dated report, see the OpenSSH SSHole security news report. This profile focuses on affected conditions, branch-specific fixes, and checks after the update.
Timeline
- 2026-11-05
OpenSSH released portable OpenSSH 10.6p2 with an sshd workaround. Alpine Linux published its package and configuration advisory.
- 2026-11-09
CISA added CVE-2026-123158 to its Known Exploited Vulnerabilities catalog.
What to do
-
Identify the affected SSH service
Inventory Linux hosts running sshd, including Alpine hosts and SSH-enabled images. Confirm musl use, PAM status, effective password authentication settings, and account password-field conditions. Prioritize reachable hosts that meet the full combination.
-
Install the branch-specific fix and restart sshd
Update to portable OpenSSH 10.6p2 or the patched distribution package for that branch. Alpine says a package upgrade does not replace a running daemon. Restart sshd and confirm the master process started after the package upgrade. Compare the installed package release with Alpine's fixed release for that branch; run sshd -V where supported.
-
Reduce exposure while updating
If the fix must wait, disable SSH password authentication after confirming key-based access works. Check the effective setting, including scoped configuration, then restart sshd. Alpine identifies this as a way to close the affected path.
-
Review possible logins
Check SSH authentication records for accepted password logins to accounts that should have no password. Review privilege use and new account or key changes on exposed hosts. Alpine advises treating a host as compromised if an unauthorized login cannot be ruled out.
What Brandefense can do
- Watch your stack for exploited flaws
Name the vendors and products you run, and Brandefense alerts you when a CVE in them is exploited.
- Vulnerability intelligence platform
Brandefense Vulnerability Intelligence follows which vulnerabilities attackers are using, so your team can patch what is under attack first.
Frequently Asked Questions
Is every OpenSSH server affected by CVE-2026-123158?
No. The cited advisories describe a narrower Linux musl, PAM-free setup with password authentication and qualifying account fields. Confirm those conditions on the running host.
Does Alpine need portable OpenSSH 10.6p2 to be fixed?
No. Alpine lists backported package fixes by branch. Compare the installed openssh package release with Alpine's branch-specific advisory and restart sshd after updating.
Does the CISA KEV listing prove my host was breached?
No. CISA added the CVE to KEV on November 9, 2026, but the catalog does not identify a breach on your host. Review local authentication evidence.