BlogVulnerability Research

SSHole (CVE-2026-123158): Patch Your Alpine Container Images

SSHole is an OpenSSH authentication bypass on musl / Alpine systems that are not using PAM. The upstream fix shipped as OpenSSH 10.6p2 on 5 November 2026. Attackers began using it in the wild roughly 40 hours later, and CISA added CVE-2026-123158 to the Known Exploited Vulnerabilities catalog on 9 November. This is a container-and-cloud attack-surface story, not a general OpenSSH news brief — the exposure in most enterprises is stale OpenSSH baked into Alpine base images, CI runners, and debug sidecars. No exploitation details below, just who is affected and what to check.

6 min readBy TigerGate Research, Security Research TeamPublished Updated

TL;DR

  • CVE: CVE-2026-123158 (SSHole). OpenSSH authentication bypass on musl / Alpine systems without PAM.
  • Fixed in: OpenSSH 10.6p2 (upstream release, 5 November 2026).
  • Exploitation: in the wild since ~6–7 November, about 40 hours after the fix landed.
  • CISA KEV: added 9 November 2026 — 21-day remediation clock for federal civilian agencies; many private contracts reference the same.
  • Your real exposure: stale OpenSSH inside Alpine-based container images, CI runners, bastions, and debug sidecars — not just production sshd.

What's affected

The affected build is OpenSSH linked against musl-libc, which in practice means Alpine Linux, when PAM is not in use. Glibc-based distributions and installations using PAM are not affected. In most enterprise estates the exposure is not the production sshd that ops carefully hardened — it is the stale OpenSSH binary that has sat in a popular Alpine base image for years and shipped forward into hundreds of derivative images. Specifically:

  • Application images based on alpine:*, node:*-alpine, python:*-alpine, ruby:*-alpine, golang:*-alpine, nginx:*-alpine, and similar.
  • CI runner images — most self-hosted GitHub Actions / GitLab runners are Alpine-based and ship OpenSSH for debugging.
  • Bastion and jump-host images, including "we don't use SSH in production, this is just for break-glass."
  • Debug sidecars and ephemeral shell containers injected into pods for operator troubleshooting.
  • Forgotten pre-prod instances — staging, QA, and old A/B environments that kept their original image pins.

"We don't expose SSH" is not sufficient. Treat reachability — including from inside the cluster, from the CI network, and from any peer VPC — as the test, not external exposure alone.

What to do

  1. Rebuild images from a base that includes OpenSSH 10.6p2 (or later) and redeploy. Pinned digests in your Dockerfiles will not pull the fix.
  2. Inventory running containers and hosts for OpenSSH version. The right question is "is an older OpenSSH present and reachable?" — not "is SSH our main access path?"
  3. Include CI runners and debug sidecars, not just production app images.
  4. Image provenance: identify every Alpine-based base image your registry publishes and prioritise those for re-base; the blast radius is usually dozens of derivative images per base.
  5. Hunt for post-exploitation on previously-reachable Alpine-based hosts: unexpected new SSH sessions after 5 November, child processes spawned by sshd, new outbound connections from SSH-reachable pods, and unfamiliar authorized_keys entries.

Companion advisory — same patch window

GPUStack (CVE-2026-102895) also landed on CISA KEV on 9 November. It gives an unauthenticated attacker admin on self-hosted model-serving infrastructure and can disclose API keys and cloud secrets. If you run containers and self-hosted inference — most teams do — one patch window should cover both.

How TigerGate helps

  • Container Security flags Alpine-derived images with OpenSSH versions below 10.6p2 across your registries, and surfaces the first running workload for each affected image so you rebuild in reachability order.
  • KSPM and CNAPP extend the view to Kubernetes pods, DaemonSets, and sidecars — including the debug and bastion containers that are easy to forget.
  • Server Vulnerability Monitoring fingerprints OpenSSH on every Linux host and cloud VM, prioritised by eBPF runtime-reachability so the hosts actually accepting SSH rise to the top of the queue.
  • Compliance evidence maps patch activity to SOC 2 CC7.1, ISO 27001 A.8.8, PCI DSS 6.3.3, and the BOD 22-01 clock on CISA KEV entries.

FAQ

SSHole is an OpenSSH authentication bypass on musl-based systems such as Alpine Linux that are not using PAM. It is fixed in OpenSSH 10.6p2. Attackers began using it around 6–7 November 2026, and CISA added it to the Known Exploited Vulnerabilities catalog on 9 November.
Check anyway. Alpine base images, CI runners, bastion hosts and debug sidecars often ship OpenSSH even when the application does not use it. The relevant question is whether an older OpenSSH is present and reachable, not whether SSH is your main access path.
Any OpenSSH build linked against musl-libc — overwhelmingly Alpine Linux — on versions before 10.6p2 when PAM is not in use. Glibc-based distributions and installations using PAM are not affected.
Public reporting puts in-the-wild exploitation roughly 40 hours after the 5 November 2026 upstream fix. CISA added the CVE to the KEV catalog on 9 November, which starts a 21-day remediation clock for federal civilian agencies under BOD 22-01.

Sources

Scan your container surface with TigerGate

14-day trial. TigerGate inventories every Alpine-derived image in your registry and every running container in your clusters, flags OpenSSH below 10.6p2, and prioritises by reachability so you rebuild in the right order.