Exploited in the wild
CVE-2026-123158: OpenSSH Password Bypass on musl Linux (Alpine)
Inttelio Threat Feeds ·
CVE-2026-123158 is a password authentication bypass in sshd in OpenSSH before 10.6p2 on Linux systems that use musl libc without PAM, such as Alpine Linux. For some account configurations, any password between 256 and 1024 characters is accepted. CISA has added it to the Known Exploited Vulnerabilities catalog, so it has been exploited in the wild.
| CVE | CVE-2026-123158 |
|---|---|
| Vendor / product | OpenBSD OpenSSH |
| CVSS v3.1 | 8.1 HIGH |
| Weakness | CWE-394 |
| Exploited in the wild | Yes - added to CISA KEV November 9, 2026 |
| CISA due date (federal agencies) | November 12, 2026 |
| Published | November 5, 2026 |
Who is affected
Organizations running sshd from OpenSSH versions before 10.6p2 on Linux where musl libc is used and PAM is not used. Alpine Linux is the example platform named in the source data. Container images built on Alpine that run sshd may also be affected; references in the data mention Docker sshd images and the Coolify platform. The bypass applies only to some account configurations, and the source data does not say which ones. Check the OpenSSH release notes and the Alpine Linux advisory for details. Systems using glibc, or using PAM for authentication, are not described as affected in the source data.
What attackers can do
A remote, unauthenticated attacker who can reach an affected SSH service may be able to log in to a vulnerable account by sending any password between 256 and 1024 characters. This applies only where password authentication is reachable and the account configuration is susceptible. A successful login gives the attacker access as that account, with high impact to confidentiality, integrity and availability (CVSS 3.1 base score 8.1, High). The attack complexity is rated High, probably because only certain configurations are exposed.
Exploitation status
Exploited in the wild. CISA added CVE-2026-123158 to its Known Exploited Vulnerabilities catalog on 2026-11-09 with a due date of 2026-11-12. CISA flags the entry as requiring forensic triage. Known ransomware campaign use is listed as Unknown. The KEV due date and BOD 26-04 bind U.S. federal civilian agencies. Contractors and private organizations should still treat the short three-day window as a sign of high urgency. Public reproduction labs are listed in the references, so working exploit details are available.
What to do now
- Inventory every system and container image running OpenSSH sshd on musl-based Linux without PAM. Start with Alpine Linux hosts and Alpine-based Docker images, and put internet-facing SSH services first.
- Upgrade OpenSSH to 10.6p2 or later, or apply your distribution's fixed package, following the OpenSSH release notes and the Alpine Linux advisory. Rebuild and redeploy any container images that bundle sshd.
- If you cannot patch right away, apply the vendor-recommended mitigations. A reasonable interim step is to disable password authentication in sshd_config (PasswordAuthentication no) and require key-based authentication. Confirm this against the vendor guidance.
- Restrict SSH exposure to trusted networks or a VPN wherever possible, especially for systems you cannot patch quickly.
- Check for compromise on affected systems, in line with CISA's forensic triage flag. Review SSH authentication logs for successful password logins you cannot explain, look for unfamiliar sessions and new accounts or SSH keys, and inspect for persistence. The source data does not provide specific indicators of compromise.
- If no fix or mitigation is available for a product or cloud service that embeds the vulnerable sshd, follow the vendor's guidance. Federal agencies must follow BOD 26-04, which includes discontinuing use of the product if mitigations are unavailable.
- Contact vendors of appliances or software that ship OpenSSH on musl to confirm whether their products are affected and when fixes will be available.
Frequently asked questions
Is my Ubuntu, Debian, or RHEL server affected by CVE-2026-123158?
Based on the source data, the flaw affects OpenSSH before 10.6p2 on Linux only when musl libc is used without PAM. Mainstream distributions like these generally use glibc and PAM, but the source data does not address them directly. Confirm with your distribution's advisory. Alpine Linux is the named example of an affected platform.
Which OpenSSH version fixes CVE-2026-123158?
OpenSSH 10.6p2 is the fixed version. Versions before 10.6p2 are affected under the conditions described: Linux, musl libc, and no PAM. Distribution package version numbers are not stated in the source data, so check the Alpine Linux advisory or your vendor's advisory.
Is CVE-2026-123158 being exploited?
Yes. CISA added it to the Known Exploited Vulnerabilities catalog on 2026-11-09 with a federal remediation due date of 2026-11-12, and flagged it for forensic triage. Whether it has been used in ransomware campaigns is listed as unknown.
Sources
- https://nvd.nist.gov/vuln/detail/CVE-2026-123158
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog
- https://github.com/leonjza/sshhole-lab
- https://github.com/openssh/openssh-portable/commit/4353fdc43ef646c43a8dda7025cc1a898caf1482
- https://github.com/predkambrij/sshhole-repro
- https://hachyderm.io/@damienmiller/117563026759098135
- https://marc.info/?l=openssh-unix-dev&m=179388064263131&w=2
- https://news.ycombinator.com/item?id=50377976
- https://news.ycombinator.com/item?id=50378228
- https://www.openssh.org/releasenotes.html#10.6p2
This briefing was drafted with AI from the official NVD and CISA records. Always confirm affected versions and fixes in the vendor advisory.
Not sure if you are exposed?
Our penetration testers find exploitable flaws before attackers do, and a vCISO can run your vulnerability program.
Talk to Inttelio