Threat level Guarded
Submit a tip

Major threats, straight to your inbox

Only the threats that matter: actively exploited flaws, big breaches and attacks that need action. No spam, unsubscribe any time.

SSHole OpenSSH Flaw CVE-2026-123158 Exploited for Root on Alpine Linux

Attackers are abusing SSHole (CVE-2026-123158), an OpenSSH flaw on musl-based Linux such as Alpine that accepts an oversized password for password-disabled accounts. One got root and dropped TAC Agent. CISA added it to KEV; OpenSSH 10.6p2 fixes it.

SSHole OpenSSH Flaw CVE-2026-123158 Exploited for Root on Alpine Linux

Threat card

Status
Actively exploited
Threat type
Vulnerabilities
Disclosed
Nov 5, 2026
Affected
OpenSSH sshd before 10.6p2 on Linux with musl libc and PAM disabled, including Alpine Linux default configuration

The short version

  • SSHole lets an unauthenticated attacker log in to accounts whose shadow password field is an asterisk by sending a 257 to 1,024 byte password.
  • Only OpenSSH on musl-based Linux with PAM disabled is affected, which includes Alpine Linux's default sshd setup.
  • Exploit code appeared about four hours after the 10.6p2 fix and GreyNoise saw a successful attack on 7 November.
  • One attacker gained root and installed the Python TAC Agent implant, while others used the flaw for botnets and cryptomining.

The SSHole OpenSSH vulnerability, tracked as CVE-2026-123158 (CVSS 8.1), is now exploited in the wild. It lets an unauthenticated attacker log in over SSH to password-disabled accounts on Linux systems that run OpenSSH on the musl C library with PAM disabled, which includes Alpine Linux’s default server setup. OpenSSH shipped the fix in 10.6p2 on 5 November 2026, exploit code followed within hours, and CISA added the flaw to its KEV catalog on 9 November. Patch or disable password authentication now, then hunt for unexpected password logins.

What happened

SSHole is an OpenSSH authentication bypass. On affected musl-based systems, an oversized password makes the password hashing call fail and return an asterisk, and sshd compares that asterisk with the asterisk stored for a password-disabled account and treats it as a match. Attackers began trying it within hours of disclosure and gained root on at least one honeypot.

The bug was found by researcher Ozgun Kultekin. According to The Hacker News, the faulty behaviour traces back to a 2016 change that fixed a username enumeration issue, CVE-2016-6210. Multiple firms, including GreyNoise, Previdian, Defused and watchTowr, have since reported exploitation, and CISA listed it alongside three other flaws in its 9 November KEV alert.

This is the second Alpine-adjacent incident on our radar in a week, after the GitLab CVE-2026-97229 exploitation against Alpine Linux’s GitLab server.

Timeline

Date (UTC where known) Event
2016 A patch for username enumeration flaw CVE-2016-6210 introduces the password handling behaviour SSHole later abuses.
5 Nov 2026 OpenSSH releases 10.6p2 with the fix; Alpine Linux publishes its advisory. Exploit code appears roughly four hours after the fix.
5 to 6 Nov 2026 Previdian logs the first exploitation attempt less than nine hours after CVE publication; exploitation attempts begin the day the proof of concept appears.
6 Nov 2026 watchTowr reports SSHole being used in botnet and cryptomining activity.
7 Nov 2026, 00:46 GreyNoise records its first successful in-the-wild exploitation, about 40 hours after the fix.
7 Nov 2026 Defused says it saw “a small amount of actors” targeting SSHole, not yet widespread.
8 Nov 2026 Previdian counts 20 attempts from 13 IP addresses in nine countries.
9 Nov 2026 CISA adds CVE-2026-123158 to KEV; Previdian’s count reaches 22 attempts from 14 IPs.
12 Nov 2026 KEV remediation due date for US federal civilian agencies.

How the attack works

Root cause

The flaw sits in sshd’s password authentication path on Linux builds linked against musl with PAM disabled. Accounts that should never accept a password are commonly locked by setting the password hash field in /etc/shadow to *. When musl’s password hashing function hits an error, it returns *, and OpenSSH mistakenly treats that output as a match for the stored value. CISA classifies it as an unexpected status code or return value weakness.

Initial access

The attack is pre-authentication and network-based. Per The Hacker News, an attacker sends an arbitrary password between 257 and 1,024 bytes long to a password-disabled account, which forces the hash attempt to fail and return the asterisk. The account must have * as its password hash; accounts with real password hashes are not bypassed.

Privilege and impact

The attacker inherits the permissions of the account. Kultekin noted that this becomes root access where the compromised account has passwordless administrative privileges, and Previdian confirmed root on an Alpine honeypot. Safe Security warns that deployment credentials, application secrets and connected infrastructure can follow, opening the door to lateral movement.

Post-exploitation seen in the wild

In chains observed by GreyNoise, attackers ran system and container reconnaissance, queried cloud metadata services, tried to read password hashes and root SSH keys, and tried to add keys to authorized_keys for persistence. One attacker gained root and installed TAC Agent, a Python command and control implant that runs shell commands, performs reconnaissance, transfers files and updates itself. It has no built-in persistence, so the operator tried to set up a startup service. Its C2 at tac.vpnla[.]org was unreachable, so it never received a task, as BleepingComputer reported. watchTowr separately tied exploitation to botnets and cryptominers.

MITRE ATT&CK mapping

Tactic Technique (ID) How it was used here
Initial Access External Remote Services (T1133) Oversized password sent to internet-facing sshd to log in to a password-disabled account.
Discovery System Information Discovery (T1082) uname and hostname run through non-interactive SSH sessions.
Discovery System Owner/User Discovery (T1033) id run after login.
Discovery Container and Resource Discovery (T1613) Container reconnaissance reported by GreyNoise.
Credential Access Cloud Instance Metadata API (T1552.005) Queries to cloud metadata services.
Credential Access /etc/passwd and /etc/shadow (T1003.008) Attempts to read password hashes.
Credential Access Private Keys (T1552.004) Attempts to read root SSH keys.
Persistence SSH Authorized Keys (T1098.004) Attempts to modify authorized_keys.
Persistence Create or Modify System Process (T1543) Startup service configured to keep TAC Agent running.
Execution Python (T1059.006) TAC Agent is a Python C2 implant.
Impact Resource Hijacking (T1496) Cryptomining activity reported by watchTowr.

Who is behind it

No single actor owns this. The TAC Agent deployment was tied by GreyNoise to an unknown threat actor it calls GT10, and the implant’s comments, logs and errors were written in Chinese, which GreyNoise says may help determine origin only alongside other evidence. A missing tool check in the implant returns feedback that could help an automated planner revise its commands, hinting at automated operation. Other exploitation feeds botnets and cryptominers. Previdian’s first observed source IP geolocated to Japan, and later attempts came from Denmark, Iran, Japan, the Netherlands, Norway, Singapore, Sweden, Switzerland and the US. Attribution beyond that is not established.

Affected products and versions

Product Affected Fixed CVE CVSS
OpenSSH (sshd) on Linux with musl libc and PAM disabled, including Alpine Linux’s default OpenSSH server configuration Versions before 10.6p2 OpenSSH 10.6p2 or the distribution’s patched package CVE-2026-123158 8.1
Not affected Dropbear, glibc-based Linux distributions, non-Linux systems, systems checking passwords through PAM, and accounts with valid password hashes.

Expect exposure to cluster in container images, lightweight cloud VMs and appliances built on Alpine, where sshd is often enabled for convenience and service accounts are locked with *.

Indicators of compromise

Type Indicator (defanged) Context
IPv4 89.116.89[.]18 Source of the first exploitation attempts seen by Previdian; ran id, uname and hostname.
Domain tac.vpnla[.]org TAC Agent C2 server (unreachable during GreyNoise’s observation).
Log pattern Accepted password for sshd success line for an account that should not accept passwords (for example alpine, root or a key-only user).
Behaviour Password field length 257 to 1,024 bytes Oversized password used to trigger the bypass.

GreyNoise publishes a live event feed for SSHole sessions, and Previdian maintains telemetry on its CVE-2026-123158 evidence page. Treat both as the reference for fresh source IPs.

Detection and hunting

Start with authentication logs. The Alpine Linux advisory tells admins to search /var/log/messages for sshd lines reading Accepted password for against any account that has no password, and to review doas use, recently created users, files and authorized keys on exposed machines.

  • Join sshd “Accepted password” events with the shadow state of the account: any success for an account whose /etc/shadow field is * is a hit.
  • Diff ~/.ssh/authorized_keys for root and service users against your configuration management baseline.
  • Look for new startup services and Python processes making outbound connections, plus any TAC Agent files.
  • From cloud workloads, alert on metadata service requests that originate from SSH sessions rather than the application.
  • In network data, flag non-interactive SSH sessions that run only short reconnaissance commands such as id, uname and hostname.

GreyNoise’s own figures are a reminder to separate noise from signal: it logged 27.5 million port 22 scans and 20.1 million attempted SSH sessions, which are not confirmed SSHole attacks. Hunt on the success condition, not on scan volume.

Mitigation and response

  1. Upgrade to OpenSSH 10.6p2 or your distribution’s patched package, then restart sshd.
  2. If you cannot patch immediately, disable SSH password authentication on affected systems.
  3. Hunt for unexpected successful password logins to accounts whose shadow field is *; if you cannot rule out a login, treat the machine as compromised, as Alpine advises.
  4. Remove unauthorised SSH keys, unknown users, startup services and TAC Agent artefacts, and block tac.vpnla[.]org and known source IPs.
  5. Rotate secrets reachable from affected hosts, including cloud instance role credentials, deployment keys and application secrets.
  6. Rebuild container images and golden images on patched Alpine bases so old sshd builds do not return on the next deploy.

Analyst take

SSHole is narrow in scope but brutal where it applies. It only bites musl builds without PAM, yet that profile describes a large share of minimal containers and cloud images, the same places that often hold instance credentials and deployment keys. Public exploit code roughly four hours after the fix, and a first confirmed success within two days, shows how quickly attackers now turn a public patch diff into working access, a pattern we also saw with the SonicWall SAML MFA bypass.

The deeper lesson is about assumptions. Teams treat an asterisk in /etc/shadow as “this account cannot log in by password”, and for a decade that held only because two components agreed on what an error looked like. Platform and DevOps teams running Alpine-based fleets should worry most: patch, but also enforce key-only SSH in configuration, so the next return value bug in the stack does not become remote access.

What to do now

0 of 6 done

Questions readers ask

Is my server affected by SSHole?

Only if it runs OpenSSH on Linux linked against musl libc with PAM disabled, such as Alpine Linux's default sshd, and has accounts with an asterisk as their password hash.

Which OpenSSH version fixes CVE-2026-123158?

OpenSSH 10.6p2, released on 5 November 2026, or your distribution's patched package, followed by an sshd restart.

How do I check if SSHole was exploited on my system?

Look for sshd Accepted password log lines for accounts that should not accept passwords, and review new users, authorized_keys and startup services.

Sources

  1. Alpine Linux: OpenSSH password authentication bypassalpinelinux.org
  2. CISA: CISA Adds Four Known Exploited Vulnerabilities to Catalogcisa.gov
  3. GreyNoise: SSHole exploitation eventssshole.events.greynoise.io
  4. BleepingComputer: Hackers exploit SSHole OpenSSH flaw to breach Linux systemsbleepingcomputer.com
  5. The Hacker News: Hackers Target OpenSSH SSHole Flaw Within Hours of Disclosurethehackernews.com
Share this story
Get the next major threat first

One short email when something serious breaks.

Threatspedia Desk

Threatspedia covers major cyber threats only, verified against primary sources. Read our editorial policy, or report a correction.

Threat alerts

Be first to know when a major threat breaks.

One short email when something serious happens, plus a weekly roundup. Free, no noise.