Threats

OpenSSH SSHole CVE-2026-123158: what OT teams should check now

SSHole, an OpenSSH password bypass on musl-based Linux without PAM, is now being probed according to SANS. OT teams should find embedded Linux devices with SSH, disable password logins and apply vendor fixes.

OTVista article cover: OpenSSH SSHole CVE-2026-123158: what OT teams should check now

A newly disclosed OpenSSH flaw, SSHole (CVE-2026-123158), lets an attacker log in to some password-disabled Linux accounts by sending a very long password, and honeypot data suggests attackers began probing for it within days of disclosure. OT teams should identify embedded Linux devices that expose SSH, disable SSH password authentication where it is not needed, restrict who can reach port 22, and apply vendor fixes through normal change control.

What happened

On 5 November 2026 the OpenSSH project released portable OpenSSH 10.6p2 with what its release notes describe as a critical security workaround for Linux systems that use the musl C library with PAM (Pluggable Authentication Modules) disabled. The project says the root cause sits outside sshd itself, but that the bug can be exploited through sshd and avoided there. The issue was reported by Özgün Kültekin of Wakefield.

According to SecurityWeek, the flaw is tracked as CVE-2026-123158 with a CVSS score of 8.1. Under the right conditions, accounts that should never accept a password, such as a key-only root account, will accept any password between 257 and 1,024 characters. SecurityWeek reports the researcher's view that distributions and build systems such as Alpine, OpenWrt, Buildroot and Yocto can be affected where they use musl without PAM.

Alpine Linux, quoted by SecurityWeek, set out the conditions for its systems: OpenSSH running without PAM, password authentication enabled, a target account whose password field is "*" (normal for key-only accounts), and at least one other local account with a SHA-256 or SHA-512 crypt hash. Alpine said every release it checked, from 3.16 to 3.24 and edge, was affected, and urged users to patch and restart sshd, or disable password logins and restart sshd.

OpenSSH developer Damien Miller explained the speed of the release by pointing to cases of rapid bug rediscovery by AI agents, which the project now sees as a reason to avoid long embargo periods.

On 9 November, Cybersecurity News reported that SANS Internet Storm Center researcher Johannes Ullrich had recorded the first clear exploit attempts against his SSH honeypots on 5 November: 232 long-password requests that day and 713 on 6 November. The report notes that these figures count suspicious requests, not confirmed compromises.

Why it matters for OT

Most enterprise Linux servers use glibc and PAM, so many IT teams will conclude they are not affected. OT environments are different. Industrial gateways, cellular and serial routers, protocol converters, edge computing boxes, HMI panels and some engineering appliances often run small embedded Linux images. Where those images are built on musl, with PAM left out to save space, and with SSH password logins enabled for field maintenance, they can match the vulnerable pattern.

The consequences in OT go beyond data access. An attacker with a shell on an edge gateway or remote access router may be able to observe or alter traffic between zones, pivot into control networks, or disrupt connectivity that operators depend on. Several practical factors raise the risk:

  • Remote access paths. Gateways and routers that provide vendor or site-to-site access are often reachable from wider networks, and sometimes from the internet.
  • Flat networks. If SSH on embedded devices is reachable from the corporate network or a shared engineering subnet, one compromised host can reach many devices.
  • Firmware-bound software. On many appliances you cannot simply update the OpenSSH package. The fix arrives only when the vendor ships new firmware, which then has to be tested and scheduled.
  • Poor visibility. Few asset registers record the C library, PAM status or SSH configuration of embedded devices, so teams may not know quickly which ones are exposed.

Who should act

Any operator in energy, water, manufacturing, oil and gas, transport or building services that runs Linux-based network or edge equipment should check exposure, particularly where SSH is used for maintenance. Integrators and OEMs that build products on Alpine, OpenWrt, Buildroot or Yocto should check their own images and tell customers whether their products are affected.

Operators working to NIS2, NERC CIP, IEC 62443 or similar requirements should record the assessment, the vendor responses and the decisions taken as part of their vulnerability management evidence. OTVista's OT vulnerability management page explains how to structure that triage.

What to do now

  1. Find SSH-enabled embedded devices. Use your asset inventory, firewall rules and passive network monitoring to list devices offering SSH on port 22 or alternative ports. Prioritise gateways, routers and edge devices that sit on zone boundaries or provide remote access. Avoid aggressive active scanning of fragile controllers.
  2. Ask vendors directly. For each product family, ask whether the firmware uses musl, whether PAM is enabled and whether password authentication is on by default. Record the answer and the vendor's fix plan.
  3. Disable SSH password authentication where it is not needed. Setting PasswordAuthentication to no blocks this attack path, according to the reporting from Cybersecurity News and Alpine's guidance. Make sure key-based or alternative access works first, and apply the change through your change management process so that maintenance access is not lost.
  4. Restrict who can reach SSH. Allow SSH to embedded devices only from approved jump hosts or management networks, and block it at zone boundaries and from the internet. A focused OT security architecture review can confirm where these conduits sit.
  5. Patch through change control. Where you run your own Alpine or similar Linux hosts in OT, such as data collectors or containers, update OpenSSH to 10.6p2 or your distribution's patched package and restart sshd. For appliances, test vendor firmware in a representative environment before deploying it during a planned maintenance window.
  6. Watch for long-password logins. Review SSH logs for successful password logins to key-only accounts, and for failures followed by success in the same session. Forward embedded device logs to central monitoring where possible.
  7. Update your inventory. Add SSH status, authentication method, OS base and firmware version to your asset records so the next embedded Linux flaw can be triaged in hours, not weeks. OTVista's OT asset inventory service page lists the attributes worth recording.

How OTVista helps

If you want support, OTVista researchers can help. Related services: OT vulnerability management, OT asset inventory and OT security architecture review. The free OT Security Quick Check is a quick way to see where to start.

Sources: OpenSSH, Release notes for OpenSSH 10.6p2; SecurityWeek, OpenSSH Rushes Patches for 'SSHole' Authentication Bypass; Cybersecurity News, Hackers Begin Exploiting OpenSSH SSHole Authentication Bypass Vulnerability

Topics: OpenSSH SSHole, CVE-2026-123158, OpenSSH vulnerability OT, embedded Linux SSH security, OT vulnerability management, OT patch triage

Frequently asked questions

What is SSHole (CVE-2026-123158)?

SSHole is a high-severity authentication bypass, rated CVSS 8.1 according to SecurityWeek, that affects the OpenSSH server on Linux systems using the musl C library with PAM disabled. Under certain account conditions, a password of 257 to 1,024 characters can be accepted for an account that should not accept passwords at all.

Is SSHole being exploited?

SANS Internet Storm Center researcher Johannes Ullrich reported long-password attempts consistent with SSHole against honeypots from 5 November 2026, as reported by Cybersecurity News. These were attempts; successful compromises had not been confirmed in that report.

Which OT devices could be affected?

Any device running OpenSSH on musl-based Linux without PAM and with password authentication enabled, which can include embedded gateways, routers and edge devices built on distributions such as Alpine or OpenWrt or on Buildroot and Yocto images. Only the device vendor can confirm whether a specific product is affected.

How can OT teams mitigate SSHole if they cannot patch?

Setting PasswordAuthentication to no in the SSH server configuration blocks this attack path, and restricting SSH access to approved management hosts reduces exposure. Any configuration change on a production device should follow change management and vendor guidance.

Which OpenSSH version fixes SSHole?

Portable OpenSSH 10.6p2, released on 5 November 2026, includes the fix. Distributions such as Alpine Linux have published patched packages, and device vendors may ship the fix in their own firmware updates.

See OTVista in action

Join the research preview or talk to us about your OT security priorities.

Join the research