Advisory

CVE-2026-123158: OpenSSH Authentication Bypass on musl libc Platforms (CVSS 8.1 HIGH)

A password authentication bypass vulnerability in OpenSSH before version 10.6p2 allows remote attackers to authenticate to some accounts using any password between 256 and 1024 characters on Linux systems using musl libc without PAM — a configuration common to Alpine Linux. The flaw is listed in the CISA Known Exploited Vulnerabilities catalog, making urgent remediation essential.

TL;DR: Upgrade OpenSSH to 10.6p2 or later immediately on all affected Linux hosts, with priority on Alpine Linux and other musl libc-based systems; if upgrading is not immediately possible, follow vendor mitigations and restrict SSH exposure at the network perimeter.

What Is the Flaw?

CVE-2026-123158 is a password authentication bypass vulnerability in OpenSSH's sshd daemon affecting versions before 10.6p2. The flaw is classified under CWE-394: Unexpected Status Code or Return Value, meaning the software misinterprets the return value of an internal function call — specifically, it fails to correctly determine whether a string is intended to be a password hash or a plaintext password.

On affected systems, this misinterpretation causes sshd to accept any password between 256 and 1024 characters as valid for certain account configurations. The bypass occurs without any special privileges, requires no user interaction, and is reachable over the network, earning it a CVSS 3.1 score of 8.1 (HIGH) with the vector CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H.

The attack complexity is rated High (AC:H), indicating that exploitation depends on specific conditions — namely the combination of musl libc, absence of PAM, and certain account configurations — rather than being universally exploitable on all OpenSSH deployments.

Who and What Is Affected?

The vulnerability affects OpenBSD OpenSSH before version 10.6p2 running on Linux systems where musl libc is used as the C standard library without PAM (Pluggable Authentication Modules) enabled. The OpenSSH project's own advisory identifies this as the relevant configuration.

Key affected scenarios include:

  • Alpine Linux — explicitly cited as an example platform using musl libc without PAM. Alpine is widely used as a base image in containerised environments and cloud-native infrastructure.
  • Any other Linux distribution or custom build that pairs OpenSSH with musl libc and operates without PAM.

The following are not affected by this specific vulnerability, based on the available facts:

  • OpenSSH deployments using glibc (e.g., most traditional Debian, Ubuntu, RHEL, and Fedora installations).
  • Deployments that have PAM enabled, as PAM provides an independent authentication path that sidesteps the vulnerable code.
  • OpenSSH 10.6p2 and later, which contain the fix.

Administrators of container orchestration platforms, CI/CD pipelines, edge appliances, and embedded or minimal Linux distributions should audit whether musl libc is in use across their estate.

Potential Impact

Successful exploitation of this vulnerability allows an unauthenticated remote attacker to bypass password authentication for affected accounts, potentially gaining full interactive shell access via SSH. The CVSS impact subscores reflect the severity:

  • Confidentiality: High — an attacker can access data and secrets accessible to the compromised account.
  • Integrity: High — the attacker can modify files, configuration, and system state.
  • Availability: High — the attacker can disrupt or destroy services on the host.

Because SSH is a privileged management channel, an authentication bypass at this layer is particularly dangerous. Depending on the account targeted, an attacker could pivot to other internal systems, exfiltrate sensitive data, plant persistent access mechanisms, or disrupt availability of critical services.

CISA has added this vulnerability to the Known Exploited Vulnerabilities (KEV) catalog (added 2026-11-09), indicating that exploitation has been observed in the wild. CISA's summary describes it as a vulnerability that "could allow for authentication bypass." Federal agencies in the United States are bound by CISA's Binding Operational Directive (BOD) 26-04 requirements regarding this vulnerability.

What To Do Now

CISA's required action for KEV entries is clear: "Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA's BOD 26-04 guidance." The following steps are recommended based on available facts:

  1. Identify affected systems immediately. Audit your environment for Linux hosts running OpenSSH before 10.6p2 on musl libc without PAM. Pay particular attention to Alpine Linux base images in containers and virtual machines.
  2. Upgrade OpenSSH to version 10.6p2 or later on all affected hosts. For Alpine Linux, this means updating via the standard package manager (apk upgrade openssh) once the patched package is available in your Alpine release channel. Verify the installed version after upgrade.
  3. Apply network-level mitigations immediately if upgrading cannot be done right away. Restrict SSH access to trusted source IP addresses using firewall rules or security groups. Do not expose sshd on musl libc systems to untrusted networks without access controls.
  4. Enable PAM as an interim compensating control where operationally feasible, as the vulnerability is specific to configurations without PAM. Consult the OpenSSH and your distribution's documentation before making authentication configuration changes.
  5. Review authentication logs for anomalous SSH login attempts, particularly long passwords or logins from unexpected source addresses, and treat any suspicious activity as potentially related to this vulnerability.
  6. Rebuild and redeploy container images based on Alpine Linux using a patched base image version as soon as one is available from the upstream maintainer.
  7. Discontinue use of the product if mitigations cannot be applied, as directed by CISA's required action for this KEV entry.

Primary references for remediation: NVD entry for CVE-2026-123158 and the CISA KEV catalog.

How Continuous External Testing Surfaces This Exposure

One of the most practical challenges with a vulnerability like CVE-2026-123158 is that the affected surface is often invisible from the inside. Teams may not have a comprehensive, real-time inventory of which externally accessible hosts run Alpine Linux or other musl libc-based systems, particularly in dynamic containerised environments where images are frequently rebuilt and redeployed.

Continuous external attack surface monitoring and testing addresses this in several ways:

  • Service enumeration: External scanning identifies hosts with SSH (port 22 or non-standard ports) exposed to the internet, including those that may have been unintentionally exposed through misconfigured security groups or firewall rules.
  • Version fingerprinting: Automated testing can detect OpenSSH version banners and flag instances running versions prior to 10.6p2, enabling rapid prioritisation before manual audits complete.
  • OS and stack identification: External probing can surface indicators consistent with Alpine Linux or other minimal distributions, helping analysts triage which exposed SSH services warrant urgent investigation.
  • Ongoing coverage: Because container images are frequently redeployed and cloud infrastructure scales dynamically, a point-in-time audit is insufficient. Continuous external testing ensures that newly spun-up instances running unpatched images are detected promptly rather than remaining in a blind spot for weeks or months.

For organisations subject to CISA's BOD 26-04 or equivalent mandates, continuous external visibility is not optional — it is a prerequisite for demonstrating that patching timelines are being met across the entire internet-facing estate.

Sources & further reading: NVD CVE-2026-123158 and the CISA KEV catalog are the authority on affected and fixed versions. Vendor/independent analysis: github.com, github.com, github.com, hachyderm.io. This advisory contains no exploit code.

Frequently asked questions

Does this vulnerability affect standard Ubuntu or Debian SSH servers?

Based on the available facts, the vulnerability is specific to Linux systems using musl libc without PAM. Ubuntu, Debian, RHEL, and similar distributions typically use glibc and often have PAM enabled by default, which means they are not expected to be affected by this specific flaw. However, organisations should verify their actual configurations, especially for any custom or minimal builds.

Is this vulnerability being actively exploited?

Yes. CISA added CVE-2026-123158 to the Known Exploited Vulnerabilities (KEV) catalog on 2026-11-09, indicating that exploitation has been observed. CISA's description confirms the vulnerability "could allow for authentication bypass." Treat remediation as urgent.

My Alpine Linux containers don't expose SSH externally — am I still at risk?

If SSH is not reachable from untrusted networks, the external risk is significantly reduced. However, internal network access, compromised adjacent systems, or misconfigured network policies could still enable an attacker to reach the vulnerable service. It is still strongly recommended to upgrade to OpenSSH 10.6p2 or later in all container images, and to audit firewall rules to confirm SSH is not accidentally exposed.

What is the fix, and where can I find the official guidance?

The fix is to upgrade OpenSSH to version 10.6p2 or later. Official guidance should be obtained from the OpenSSH project and your Linux distribution's security advisories. The CISA KEV catalog entry and the NVD entry for CVE-2026-123158 are authoritative primary sources for required actions and additional references.