CISA added SSHole (CVE-2026-123158) to its Known Exploited Vulnerabilities (KEV) catalog on November 9, 2026, citing evidence of active exploitation. The flaw affects a specific set of Linux OpenSSH configurations, not every SSH server; OpenSSH released a workaround, and Alpine Linux published fixed package versions for its branches. CISA’s alert OpenSSH’s release notes Alpine’s advisory
What SSHole affects
SSHole is a password-authentication bypass in OpenSSH’s sshd, the program that handles incoming SSH connections. OpenSSH describes the affected setup as some Linux systems built and run without PAM, an authentication framework. Alpine’s advisory describes the affected path on systems using musl, a C library that provides functions including password-hash calculations.
For the Alpine conditions, the SSH service must be reachable, PasswordAuthentication must be enabled, and the target account must be eligible for SSH login with * in its password field. At least one other local account must have a password hash beginning with $5$ or $6$. Alpine specifies that the relevant authentication path must also be in use.
The mechanism hinges on how a long password is handled. Alpine says a password of 257–1024 bytes can make musl’s crypt() function return * as an error value. In the affected path, that returned marker can match the * stored in the target account’s password field, allowing sshd to accept the login.
Match the installed package to the Alpine branch, then restart sshd after upgrading; installing the fix alone does not replace the running service.
Which setups are outside Alpine’s described conditions?
Alpine identifies PasswordAuthentication no, PAM-enabled openssh-server-pam with UsePAM yes, accounts locked with !, and systems without a local $-style password hash as outside the affected conditions it describes. A service must be reachable for an attacker to attempt the bypass.
Alpine’s official tiny-cloud images from versions 3.18.11 through 3.24.3 have a more specific case: they include an alpine account with a disabled password and passwordless doas. Alpine says those images are safe on first boot; the described exposure arises if a compatible $6$ hash is later added. That scenario concerns those image versions and account setup.
How to update OpenSSH on Alpine Linux
OpenSSH 10.6p2, released November 5, 2026, includes the upstream workaround. Alpine backported fixes to its package branches, so Alpine operators should match their branch to the corresponding fixed openssh version rather than rely on the upstream version number alone.
| Alpine branch | Fixed openssh package version |
| edge | 10.6_p2-r0 |
| 3.24 | 10.3_p1-r2 |
| 3.23 | 10.2_p1-r1 |
| 3.22 | 10.0_p1-r11 |
| 3.21 | 9.9_p2-r1 |
| 3.20 | 9.7_p1-r6 |
| 3.19 | 9.6_p1-r3 |
| 3.18 | 9.3_p2-r4 |
| 3.17 | 9.1_p1-r7 |
| 3.16 | 9.0_p1-r6 |
After installing the fixed package, restart the SSH service with Alpine’s command rc-service sshd restart. Alpine says upgrading the package does not replace the running sshd process.
If reviewing a host for signs of access, Alpine advises checking /var/log/messages for sshd entries that say Accepted password for an account with no password. It also recommends reviewing doas use and checking for newly created users, changed files, and changes to authorized_keys.
What the later activity records and CISA guidance say
GreyNoise’s SSHole tracker contains dated activity records through November 17, 2026, including observations of shell commands. Those entries are records from GreyNoise’s tracker, not a count of affected systems worldwide. GreyNoise’s SSHole tracker
CISA’s November 9 alert also added three other vulnerabilities to KEV: improper authentication in GPUStack (CVE-2026-102895), code injection in SignalWire FreeSWITCH (CVE-2026-116779), and incorrect authorization in IBM Aspera Faspex (CVE-2026-123218). The alert’s active-exploitation basis applies to the four catalog additions; the SSHole conditions described above are specific to OpenSSH.
CISA says Binding Operational Directive 26-04 applies to Federal Civilian Executive Branch agencies and encourages other organizations to prioritize KEV vulnerabilities through risk-based vulnerability management.