Skip to content
Server Security Center
KEVhigh8.1

CVE-2026-123158: OpenBSD OpenSSH Unexpected Status Code or Return Value

OpenBSD OpenSSH · listed in the CISA catalog of actively exploited vulnerabilities since 2026-11-09.

CVSS v3.1 (CVE record)
8.1
high
EPSS (exploit probability, 30 days)
88%
higher than 99.7% of all CVEs
Added to CISA KEV
2026-11-09
US federal due date 2026-11-12
Ubuntu priority
high

CVE-2026-123158 explained

CVE-2026-123158 is a password authentication bypass in sshd from OpenSSH before 10.6p2 on Linux. It applies when musl libc is used without PAM, because sshd lacks a workaround for misinterpreting whether a string is a password hash. For some account configurations, any password between 256 and 1024 characters is accepted. CISA lists it as known exploited.

Impact

A remote attacker without credentials or user interaction could log in over the network to affected accounts and gain high impact on confidentiality, integrity and availability. Attack complexity is high. The bypass only occurs on Linux systems where sshd uses musl libc without PAM, and only for some account configurations. Alpine Linux is named as an example of such a platform. Systems not matching these conditions are not described as affected.

Who is affected

Debian 14 (forky), the testing distribution, has fixes in openssh and openssh-gssapi version 1:10.6p2-1. Debian 12 (bookworm) and Debian 13 (trixie) list openssh as unimportant with no fix planned. On Ubuntu, openssh-ssh1 has no fixed version published for 18.04 LTS, 20.04 LTS, 22.04 LTS, 24.04 LTS, 26.04 LTS and 26.10. Ubuntu 18.04 LTS and 20.04 LTS are out of standard support and receive fixes only through Ubuntu Pro (ESM).

Written with AI from the data on this page and checked against it automatically.

Official description

sshd in OpenSSH before 10.6p2 on Linux, when musl libc is used without PAM, lacks a workaround for a password authentication bypass (related to misinterpretation of whether a string is intended to be a password hash). For some configurations of accounts, any password between 256 and 1024 characters succeeds.

An example of a platform using musl libc without PAM is Alpine Linux.

CISA required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk guidance and CISA’s “Forensics Triage Requirements”. Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.

CISA notes

Upstream versions (CVE record)

From the CVE record published by the vendor or CVE numbering authority.

  • OpenBSD OpenSSHLinux
    Affected
    • < 10.6p2
    Fixed in
    • 10.6p2

Ubuntu and Debian releases

A server is vulnerable if it has a package built from the listed source package installed in a version lower than the fixed version for its release.

What to do

  1. Identify hosts running sshd from OpenSSH before 10.6p2, especially any using musl libc without PAM.
  2. On Debian 14 (forky), update openssh and openssh-gssapi to 1:10.6p2-1 or later, then restart sshd.
  3. On other releases, track the Debian and Ubuntu advisories and install fixed packages when they are published.
  4. Restrict network access to SSH so only trusted hosts and networks can reach it.
  5. Review SSH login logs for unexpected successful logins on exposed systems.
  6. Move Ubuntu 18.04 LTS and 20.04 LTS systems to Ubuntu Pro or upgrade them to a supported release.

Until fixed packages exist, limit who can reach sshd using firewalls or access controls, and avoid exposing SSH directly to the internet. Confirm whether your systems match the affected condition of musl libc without PAM. Watch the distribution advisories for updates. For Ubuntu 18.04 LTS and 20.04 LTS, use Ubuntu Pro or upgrade to a supported release.

Written with AI from the data on this page and checked against it automatically.

Check and fix on a server

Run on each Ubuntu or Debian server. Replace openssh with the source package from the table above (this CVE affects 3 source packages).

1. Show installed packages built from the source package, with their versions

dpkg-query -W -f='${binary:Package} ${Version} ${source:Package}\n' | awk '$3=="openssh"'

2. Compare each installed version with the fixed version for your release from the table (releases with a fixed version only)

I=INSTALLED_VERSION; F=FIXED_VERSION   # replace both
dpkg --compare-versions "$I" lt "$F"; case $? in 0) echo vulnerable ;; 1) echo "fixed or newer" ;; *) echo "check the versions" ;; esac

3. Install the fix

sudo apt update && sudo apt install --only-upgrade $(dpkg-query -W -f='${binary:Package} ${source:Package}\n' | awk '$2=="openssh"{print $1}')

Services keep running the old code until they are restarted – restart the affected service or check with needrestart.

No fixed version yet on 8 releases

Ubuntu 26.10, Ubuntu 26.04 LTS, Ubuntu 24.04 LTS, Ubuntu 22.04 LTS, Ubuntu 20.04 LTS, Ubuntu 18.04 LTS, Debian 13 (trixie), Debian 12 (bookworm): no fixed version of the affected packages yet, so every installed version there is affected. Until a fix is published:

  • Follow the vendor's advisory for a mitigation or patch: github.com/openssh/openssh-portable/commit/4353fdc…
  • If the server does not need the package, remove it, or replace it with a maintained alternative.
  • Restrict exposure: keep the affected service off the internet, limit access with a firewall or VPN, and turn off the vulnerable feature where you can.

This page updates automatically when Ubuntu or Debian publish a fix.

CISA's assessment (SSVC)

Exploitation
Exploited in the wild
Automatable
No – each attack needs manual steps
Technical impact
Total – full control of the component or total information disclosure

Weakness: CWE-394 Unexpected Status Code or Return Value

Questions about CVE-2026-123158

Are standard Debian and Ubuntu systems affected?
The description limits the bypass to sshd on Linux using musl libc without PAM, with Alpine Linux as an example. Debian rates it unimportant for bookworm and trixie. Ubuntu lists openssh-ssh1 as affected with no fix published yet.
Is this vulnerability being exploited?
Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2026-11-09, with a US federal due date of 2026-11-12. Known ransomware use is listed as unknown.
Do I need to restart anything after updating?
Yes. Running sshd processes keep using the old code until the service is restarted after the package update.

Written with AI from the data on this page and checked against it automatically.

References

Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-21. Always confirm with the vendor's or distribution's advisory before patching.