GreyNoise’s event page lists IP addresses tagged as sending the CVE-2026-123158 exploit and commands run by spawned shells. The latest displayed command timestamp is Nov. 17, 2026. OpenSSH 10.6p2 contains the upstream workaround, while Alpine Linux lists fixed package versions by branch. GreyNoise’s event data records activity in its honeypot telemetry, not a worldwide count of compromised systems.
What the telemetry and CISA listing show
GreyNoise’s records include exploit-sending IPs and commands run by shells spawned in its honeypot environment, including system identification and reconnaissance involving account and SSH-key files. That makes the records evidence of activity beyond incoming connection attempts, within GreyNoise’s monitored systems.
CISA added CVE-2026-123158 to its Known Exploited Vulnerabilities catalog on Nov. 9, 2026. The CISA entry lists Nov. 12 as its due date and marks use in ransomware campaigns as unknown.
Which OpenSSH configurations are affected
OpenSSH describes the vulnerability as a password-authentication bypass through sshd on some Linux systems built and run without PAM, or Pluggable Authentication Modules, a framework for handling authentication. The issue involves musl and a particular password-hash handling path; it does not apply to Linux systems as a whole. OpenSSH’s release notes describe the affected scope, while Red Hat’s bug tracker describes the hash-interpretation flaw.
Ars Technica reports that the vulnerable configuration also requires password authentication and a particular combination of local account entries: one with * in /etc/shadow and another with a SHA-256 or SHA-512 password hash. The reported mechanism involves musl’s password-hashing function returning * for an overlong input, which can be mistaken for the stored value for the affected account.
Find the fixed package for your Alpine branch
OpenSSH released version 10.6p2 on Nov. 5, 2026, with the upstream workaround. Alpine’s security tracker lists these fixed OpenSSH package versions for the branches shown:
| 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.7_p2-r5 and 9.6_p1-r3 |
The Alpine security tracker lists distribution-specific fixes, so a corrected Alpine package does not necessarily use the upstream 10.6p2 version string.
Match the fix to the Alpine branch you run; the upstream version number alone will not identify every fixed Alpine package.
Secure.com’s remediation guidance says to restart sshd after upgrading so the running daemon uses the updated code. Container images and already-launched instances based on older cloud images need their own update or rebuild.