The SSHole authentication bypass in OpenSSH (CVE-2026-123158) was weaponised within hours of its patch. CISA has added it to the Known Exploited Vulnerabilities catalogue.
An authentication bypass flaw in OpenSSH, nicknamed SSHole, moved from public disclosure to real-world attacks in a matter of hours. Tracked as CVE-2026-123158 and rated 8.1 on the CVSS scale, it affects OpenSSH servers running on Linux systems built with the musl C library where PAM authentication is switched off. Alpine Linux, with its default OpenSSH configuration, is the most common affected setup.
The root cause is sloppy error handling in password verification. When an attacker supplies a password longer than 257 bytes, the musl hashing function cannot complete and returns an asterisk (*). OpenSSH mistakes that return value for a valid stored hash on accounts where password login has been deliberately disabled, and lets the session through. The result is remote access to accounts that should never accept a password at all, and root access where that account carries administrative privileges.
Exploit code public four hours after the fix
The OpenSSH project shipped the fix in version 10.6p2 on 5 November 2026. According to BleepingComputer, proof-of-concept exploit code appeared roughly four hours later and exploitation attempts started the same day. Threat intelligence firm Previdian told The Hacker News it saw the first attempt less than nine hours after the CVE was published, and confirmed successful root access on a honeypot running Alpine Linux. The US cybersecurity agency CISA added the flaw to its Known Exploited Vulnerabilities catalogue on 9 November 2026.
Post-access behaviour has been documented too. Attackers run reconnaissance commands, harvest credentials, write their own keys into authorized_keys for persistence, and drop cryptocurrency miners and botnet components. Patching alone therefore does not close the case: anyone running an exposed server needs to establish whether someone walked in while the window was open.
Why this matters for smaller companies
This is not a problem confined to large cloud providers. musl-based Alpine Linux is everywhere in container images, small virtual servers, NAS appliances and embedded network equipment. A company with no data centre of its own can still be exposed through the server hosting its website, the virtual machine running its accounting software, or the backup appliance sitting in the office. In many of those deployments the SSH port is left reachable from the internet.
There is a compliance dimension as well. Article 12 of Türkiye's Personal Data Protection Law (KVKK, Law No. 6698) requires data controllers to maintain an appropriate level of security. Under the 2026 schedule published by the Turkish Data Protection Authority, failure to meet data security obligations carries an administrative fine between TRY 256,357 and TRY 17,092,242. Leaving a published, actively exploited flaw unpatched for days is a difficult position to defend if a breach follows.
What we recommend at Kamer Bilişim
- Inventory first, then patch. List every server, container and network device running OpenSSH along with its version. Move to 10.6p2 or your distribution's patched package and restart the sshd service. Confirm the version after patching rather than assuming the update landed.
- Keep SSH off the open internet. Put administrative access behind a VPN or an IP-restricted firewall rule, disable password authentication and move to key-based logins. The flaw simply does not work where password authentication is not in play.
- Look backwards, not just forwards. Review SSH session logs since 5 November, check authorized_keys files for unexpected entries, look for newly created accounts and unexplained CPU load. If anything looks wrong, patching the system is not a sufficient response on its own.
We can review whether your server and network estate is exposed to this flaw and plan the patching and hardening work as part of a corporate maintenance agreement. Get in touch through our contact page to arrange an assessment.
Source: BleepingComputer, The Hacker News, CISA KEV catalogue, Turkish Data Protection Authority 2026 administrative fine schedule.
Source: BleepingComputer