OpenSSH Vulnerability in Las Vegas: Attackers Logged In Within Hours of Disclosure
A bug nicknamed “sshole” lets anyone walk into passwordless Linux accounts. Here is what to check before the weekend.
Published by CMIT Solutions of Las Vegas · Cybersecurity · 5 min read
What the OpenSSH Vulnerability Means for Las Vegas Businesses
This OpenSSH vulnerability (CVE-2026-123158) is already being exploited. Threat intelligence firm Previdian saw its first attack attempt less than nine hours after the CVE was published, and confirmed root access on a honeypot running real Alpine Linux. If your Las Vegas business runs Linux servers, containers or network appliances, someone on your team or at your IT vendor needs to check them today.
Researcher Özgün Kültekin nicknamed the flaw “sshole.” It affects OpenSSH versions before 10.6p2 on Linux systems that use musl libc and do not check passwords through PAM. Alpine Linux’s default OpenSSH package fits that description. So do a lot of Docker images, and the article reporting the flaw also lists OpenWrt, Buildroot and Yocto as worth checking.
Fewer than nine hours passed between publication of the CVE and the first observed attack. Your patch window is measured in hours, not weeks.
How the OpenSSH Flaw Works
Some Linux accounts have no usable password: root, key-only deploy users, LDAP users, and the default user on Alpine’s AWS and Azure images. In the shadow file those accounts show a “*” instead of a password hash. The bug makes them accept any password longer than 256 characters.
- Root cause: a 2016 OpenSSH change (for CVE-2016-6210) borrows another account’s salt when no usable hash exists. musl’s crypt() has refused SHA-256 and SHA-512 passwords over 256 bytes since 2012 and returns “*” on failure. That result matches the “*” on a passwordless account, so sshd lets the user in.
- Requirements: password logins must be enabled (the OpenSSH default). The researcher’s testing found only the musl build without PAM affected.
- Not affected: glibc systems such as Debian, Ubuntu and Fedora, PAM setups, Dropbear and OpenBSD, according to the researcher.
- Exploitation so far: Previdian logged eight attempts from one Japan-based IP address, using oversized passwords followed by quick reconnaissance commands. No threat actor has been named, and CISA had not added the bug to its Known Exploited Vulnerabilities catalog at the time of reporting.
What’s at Stake for Las Vegas Businesses
Most Las Vegas offices don’t knowingly run Alpine Linux. The risk sits in the things nobody inventoried: a container a contractor built, a firewall or router with embedded Linux, a cloud server spun up for a project and forgotten.
- ⚠Hospitality and gaming operators with cloud-hosted loyalty, booking or reporting tools built on lightweight containers.
- ⚠Healthcare practices whose patient-data integrations run on servers a vendor manages for them.
- ⚠Government contractors who must report an incident if an unpatched server is reached.
- ⚠Construction and professional-services firms using cloud servers for file sharing and project tools that no one has reviewed in a year.
Three Steps to Close This OpenSSH Vulnerability
• Step 1: Find every system running OpenSSH
The GapMost small businesses can’t list the servers, containers and appliances that accept SSH connections. You can’t patch what you haven’t found.
The FixAsk your IT provider and any outside developers for a list of everything reachable on SSH, including cloud servers and Docker images. Flag anything built on Alpine or another musl-based system.
• Step 2: Patch to 10.6p2, then restart the service
The GapUpdating the package does not restart the running sshd. The old, vulnerable process keeps accepting connections until someone restarts it.
The FixOpenSSH 10.6p2 shipped November 5, and Alpine pushed patched packages for branches 3.16 through edge the same day. Install the update, restart sshd, and rebuild any container image that bundles the old version. Until you can, set PasswordAuthentication to no, as OpenSSH developer Damien Miller advises.
• Step 3: Check the logs for a login that shouldn’t have happened
The GapThe attacks use a normal-looking password login, so nothing alarms unless someone reads the log. Public proof-of-concept exploits are also circulating on GitHub, and Previdian warns they are unverified and could contain malware.
The FixSearch /var/log/messages for “Accepted password for” entries naming root, alpine or key-only accounts. Review new users and authorized_keys files. If you can’t rule out a login, treat the machine as compromised. Don’t test public exploit code on a production system.
Las Vegas Businesses: Don’t Wait for the Breach.
Not sure what’s running on your servers? We’ll help you find out.
Defending Las Vegas with CMIT Solutions
CMIT Solutions of Las Vegas works with Clark County businesses in healthcare, gaming, hospitality, construction and professional services. We keep an inventory of what’s exposed, patch on a schedule, and watch for odd logins around the clock with 24/7 managed detection and response. When a bug like this lands on a Thursday, our clients already know what they’re running.
Help Net Security: OpenSSH flaw exploited in the wild just hours after disclosure (CVE-2026-123158), Nov 6, 2026
Help Net Security: November 2026 Patch Tuesday forecast, Nov 6, 2026
Protect Your Las Vegas Business Today
Get a clear picture of what’s exposed and a plan to fix it.
Prefer to talk? Call (702) 725-2877 or email LVSales@cmitsolutions.com