Skip to content
securitytabs

Updated · 1 update

OpenSSH "sshole" flaw lets attackers log in to passwordless accounts on musl-based Linux

A flaw in the remote-login software OpenSSH lets an attacker sign in without a password to certain accounts on Alpine Linux and similar systems, and attackers are already using it. Organizations running affected systems should update now.

OpenSSH login bypass on musl-based Linux exploited
OpenSSH login bypass on musl-based Linux exploited

What's new

  1. Added the fixed version, SecurityWeek's reporting on who is behind the first attempts, and the reference to the other flaws CISA listed the same day. [1]

TimelineWhat should my organization do?

Vulnerabilities

What happened

OpenSSH fixed CVE-2026-123158, nicknamed sshole, in version 10.6p2 on 5 November 2026. The flaw affects Linux systems that run OpenSSH on the musl C library with Pluggable Authentication Modules (PAM) disabled. Horizon3.ai says this includes Alpine Linux in its default configuration. [2][3][4]

The flaw lets a remote attacker sign in to accounts that have no password set. The Alpine Linux team is quoted as saying an attacker who can reach the SSH port needs one connection and no password. [2][3]

Exploitation

Threat intelligence firm Previdian warned that attackers were exploiting the flaw within hours of disclosure. The SANS Internet Storm Center reported an increase in exploit attempts against its SSH honeypots on 8 November. [2][3][5]

CISA added the flaw to its Known Exploited Vulnerabilities (KEV) catalogue, its list of flaws attackers are using, on 9 November, with a federal due date of 12 November. It listed three other flaws the same day, in GPUStack, FreeSWITCH and IBM Aspera Faspex. NVD rates the OpenSSH flaw 8.1 on the CVSS scale. CISA lists known ransomware use as unknown. [6][7]

BleepingComputer reports attackers are running commands, stealing credentials and setting up persistent access. SecurityWeek reports the first attempts are attributed to botnets and crypto miners, and that other threat actors are expected to follow. [8][1]

Fixes

OpenSSH releases before 10.6p2 are affected, according to the advisory republished on 9 November. [9]

Timeline

  1. CISA added the flaw to its Known Exploited Vulnerabilities catalogue. [6]

  2. · CISA KEV

    CISA added CVE-2026-123218 to its Known Exploited Vulnerabilities catalog.

  3. · CISA KEV

    CISA added CVE-2026-123158 to its Known Exploited Vulnerabilities catalog.

  4. · CISA KEV

    CISA added CVE-2026-116779 to its Known Exploited Vulnerabilities catalog.

  5. The SANS Internet Storm Center reported rising exploit attempts against its honeypots. [5]

  6. Previdian warned that attackers were exploiting the flaw within hours of disclosure. [2][3]

  7. OpenSSH released version 10.6p2 to fix the flaw. [2][9]

Update history

  1. Added the fixed version, SecurityWeek's reporting on who is behind the first attempts, and the reference to the other flaws CISA listed the same day. [1]

  2. First published

Explained

The technology and terms in this story. Learn more

Business ActionWhat this means inside your organization, and what to do about it, by company size.

Small business

No dedicated security staff; relies on providers

What to know

Small businesses are mostly exposed through servers or devices run by a provider; Alpine Linux systems with SSH reachable are the ones named as affected. [4]

What to do

  1. Ask your IT or hosting provider whether any Alpine Linux or musl-based systems expose SSH and whether OpenSSH is at 10.6p2 or later. [9][4]
  2. If you manage such a server yourself, update OpenSSH to the fixed release. [9]

Mid-size company

A small IT or security team

What to know

CISA lists the flaw as exploited, and Previdian reports attacks began within hours of disclosure. [6][2]

What to do

  1. Inventory Linux hosts running OpenSSH on musl, including Alpine-based servers and containers, and update to the fixed release. [4][9]
  2. Review SSH authentication logs for unexpected logins to accounts without passwords since early November. [5][2]

Large enterprise

A security operations team

What to know

Exploitation is reported in the wild, including credential theft and persistence, so exposed hosts may need compromise checks as well as patching. [8][6]

What to do

  1. Find musl-based OpenSSH deployments with PAM disabled across servers and container images, and move them to the fixed release. [4][9]
  2. Hunt for successful SSH logins to passwordless accounts and for new credentials or persistence on hosts that were reachable on SSH since early November. [8][5]

Sources

  1. [1]SecurityWeek · Nov 9, 12:13 UTC
    Hackers Exploiting ‘SSHole’ Authentication Bypass in OpenSSHcontext
  2. [2]Help Net Security · Nov 6, 12:49 UTC
    OpenSSH flaw exploited in the wild just hours after disclosure (CVE-2026-123158)context
  3. [3]The Hacker News · Nov 6, 15:21 UTC
    Hackers Target OpenSSH SSHole Flaw Within Hours of Disclosure, Gain Root on Honeypotcontext
  4. [4]Horizon3.ai · Nov 6, 23:29 UTC
    CVE-2026-123158 | OpenSSH musl Password Authentication Bypass & Remote Code Execution Vulnerability (*sshole)context
  5. [5]US-CERT / SANS Internet Storm Center · Nov 8, 15:44 UTC
    Scans for Sshole Vulnerability (CVE-2026-123158), (Sun, Nov 8th)context
  6. [6]CISA Advisories · Nov 9, 12:00 UTC
    CISA Adds Four Known Exploited Vulnerabilities to Catalogcontext
  7. [7]Security Affairs · Nov 10, 21:31 UTC
    U.S. CISA adds IBM, SignalWire FreeSwitch, OpenSSH, and GPUStack flaws to its Known Exploited Vulnerabilities catalogcontext
  8. [8]BleepingComputer · Nov 9, 16:04 UTC
    Hackers exploit SSHole OpenSSH flaw to breach Linux systemscontext
  9. [9]Canadian Centre for Cyber Security · Nov 9, 18:34 UTC
    OpenBSD security advisory (AV26-1130) - Update 1context