ServicesManaged IT servicesMicrosoft 365CybersecurityCloud & projectsManaged IntelligenceWhy MSP LogicHealth checkSecurityReviewsBlogsSecurity NewsAboutBook
SECURITY NEWS

OpenSSH SSHole flaw exploited: patch Linux now

The OpenSSH SSHole flaw, CVE-2026-123158, lets attackers log in to locked accounts on Alpine and other musl-based Linux systems, and it is now being exploited. Here's who is affected and what Australian businesses should do.

Source: BleepingComputer – Hackers exploit SSHole OpenSSH flaw to breach Linux systems

If your business runs Linux servers, cloud virtual machines or network devices that accept SSH logins, check them this week. A flaw in OpenSSH nicknamed SSHole lets attackers sign in to accounts that were meant to be locked, and it is now being used in real attacks.

What happened

On 5 November 2026 a security researcher disclosed SSHole, tracked as CVE-2026-123158. The OpenSSH team shipped a fix the same day in OpenSSH 10.6p2, describing it as a critical security workaround for Linux systems that use the musl C library with PAM disabled. Exploit code appeared within hours of the release.

BleepingComputer reported on 9 November 2026 that several security firms have now confirmed exploitation. Attempts started on 5 November, and one threat intelligence company recorded its first successful break-in on 7 November, roughly 40 hours after the fix came out. Attackers who got in ran reconnaissance, queried cloud metadata services, tried to read password hashes and root SSH keys, and tried to add their own SSH keys so they could come back later. In one case an attacker gained root and installed a remote-control agent. Another firm linked the activity to botnets and cryptomining.

The reported activity is not yet widespread, but the pattern is familiar: a public fix, a public exploit, and attackers scanning for anyone who hasn't updated.

Who is affected

SSHole is narrow, which is good news, but the systems it hits are easy to forget. According to the researcher's findings as reported by BleepingComputer, all of these need to be true:

  • OpenSSH runs on a Linux system built on the musl C library, such as Alpine Linux, OpenWrt, Buildroot or Yocto.
  • PAM authentication is turned off (the default in Alpine's OpenSSH server package).
  • SSH password logins are allowed.
  • At least one account is locked with an asterisk (*) in place of a password hash, and another account has a normal password.

The trick is simple: an oversized password makes the password check fail in a way OpenSSH mistakes for a match on the locked account. It does not bypass real passwords. Mainstream distributions that use glibc, such as Debian, Ubuntu and Fedora, and systems using PAM are not vulnerable.

One detail stands out. The researcher warned that Alpine Linux's official AWS and Azure cloud images include a default alpine account with passwordless administrator rights, so a successful login there can lead straight to full root control.

Why it matters for Australian businesses

Most small businesses don't knowingly run Alpine Linux, which is exactly the problem. It is popular for lightweight cloud servers and containers that a developer or past provider may have set up and left running. Buildroot, Yocto and OpenWrt sit underneath a lot of routers, appliances and embedded devices. These systems rarely appear on anyone's patch list.

A compromised server can be used to mine cryptocurrency on your cloud bill, steal keys that unlock other systems, or give an attacker a quiet foothold for later. The Australian Cyber Security Centre's Essential Eight guidance treats prompt patching of internet-facing systems as a core control, and this is a clear case for it.

What to do now

  1. List what accepts SSH. Identify any Linux servers, cloud VMs, containers and network devices in your business that can be reached over SSH, particularly from the internet.
  2. Find the musl-based ones. Check which of those run Alpine Linux or are devices built on OpenWrt, Buildroot or Yocto. Systems on Debian, Ubuntu or Fedora are not affected by this flaw.
  3. Update OpenSSH. Install OpenSSH 10.6p2 or your vendor's fixed package. On Alpine, that is apk upgrade openssh. For appliances, check the manufacturer for firmware updates.
  4. Turn off SSH password logins. If you can't update straight away, set PasswordAuthentication no in the SSH server configuration and restart SSH. Key-based logins are the better long-term setup anyway.
  5. Look for signs of a break-in. Check SSH logs for successful password logins to accounts that should be locked (such as the default alpine account), unfamiliar entries in authorized_keys files, and unexpected new startup services.
  6. Limit who can reach SSH. Restrict SSH to a VPN or known IP addresses rather than leaving it open to the whole internet.

How MSP Logic can help

If you're not sure what is running SSH in your offices or cloud accounts, we can find it, apply the OpenSSH fix, switch to key-based logins and review logs for anything suspicious. That work sits under our cybersecurity services, and we can keep servers and devices on a regular patch schedule as part of managed IT services.

Want us to check your Linux servers and devices? Get in touch and we'll take a look.

Source: BleepingComputer – Hackers exploit SSHole OpenSSH flaw to breach Linux systems. This article is MSP Logic's own summary and advice; read the original report for full details.

NEED A HAND?

Want us to check this for you?

Book a free, no-obligation IT review and we'll show you where you stand and what to fix first.