Philips posted an advisory on November 9 saying no Philips products are known to be affected by CVE-2026-123158, an OpenSSH authentication bypass that CISA added to its Known Exploited Vulnerabilities catalog the same day. The KEV entry carries a November 12 remediation deadline for federal civilian agencies under Binding Operational Directive 26-04.

Researcher Ozgun Kultekin disclosed the flaw, which he named SSHole, after building sshd in dozens of configurations and sending roughly 17,600 unusual login attempts. He found that systems using the musl C library without PAM, Alpine Linux chief among them, accept a password longer than 256 characters for any account whose password field holds a bare asterisk, including root, key only users, LDAP accounts, and the default cloud user on Alpine's AWS and Azure images.

The bypass stacks three separate design choices. Accounts meant never to accept a password store an asterisk instead of a hash. A 2016 OpenSSH fix for user enumeration, CVE-2016-6210, made sshd borrow another account's salt and hash the submitted password when an account has no usable hash. And musl's crypt function, since 2012, rejects any SHA-256 or SHA-512 password over 256 bytes and returns the same asterisk, which then matches the locked account's stored value and lets sshd accept the login.

OpenSSH fixed the flaw in version 10.6p2 on November 5, and Alpine Linux shipped patched packages the same day across branches 3.16 through edge. Threat intelligence firm Previdian reported exploitation beginning less than nine hours after the CVE was published, confirming root access on an Alpine honeypot from a single Japan based IP address that ran id, uname, and hostname after logging in with an oversized password.

The affected configuration reaches beyond Alpine's cloud images. The same musl-without-PAM combination ships in OpenWrt, Buildroot, and Yocto based firmware, and in many minimal Docker images used to package network services, so a hospital's OT and IoT inventory is a more useful place to check than its Philips asset list alone. Systems on glibc distributions such as Debian, Ubuntu, and Fedora, or that use PAM, Dropbear, or OpenBSD, are not affected.

Philips framed this the same way it has treated the past month's Cisco, BeyondTrust, and Ivanti exploited-flaw notices: a quick statement that no shipped product runs the affected stack, filed inside the KEV clock rather than after it. Device owners should read the no-impact finding as limited to Philips branded products, not as clearance for any Alpine based appliance, container, or embedded gateway elsewhere on a clinical network.