NVD published CVE-2026-123158 on November 5, 2026. CISA added it to the Known Exploited Vulnerabilities catalog on November 9, with a due date of November 12. Three days, for a component that sits on nearly every Linux server.
The scope is narrow, though. The flaw only affects sshd on Linux with musl libc and without PAM, and NVD names Alpine Linux as an example platform. In practice, that means a large share of the Docker images that ship an SSH server.
The vulnerability
| Field | Value |
|---|---|
| CVE | CVE-2026-123158 |
| CVSS 3.1 (MITRE, CNA) | 8.1 (HIGH) — AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H |
| Type | Unexpected status code or return value (CWE-394) |
| NVD status | Modified |
| NVD published | 2026-11-05 |
| Added to CISA KEV | 2026-11-09 |
| CISA due date | 2026-11-12 |
| Fixed version | OpenSSH 10.6p2 |
From the NVD description:
For some configurations of accounts, any password between 256 and 1024 characters succeeds.
NVD has not scored this entry itself: the score comes from MITRE acting as the CNA.
How it works
According to NVD, sshd lacks a workaround for a musl behavior: on that libc, password checking can misread what a string is, treating it as a password hash rather than a password. For some account configurations, the upshot is that any password from 256 to 1024 characters is accepted.
So three conditions have to line up:
sshdruns on Linux with musl (Alpine and images built on it);- it is built or configured without PAM;
- password authentication is enabled for the targeted account, and that account is in an affected configuration.
The AC:H in the vector reflects those conditions. Once they are met, nothing else stands in the way: no account, no user interaction.
Why it hit KEV in four days
CISA does not describe the exploitation. But the NVD references go a long way toward explaining the speed: a public demo lab repository, a public reproduction repository, a dedicated website, and a GreyNoise page tracking the event. A bug triggered by a 256-character string needs no sophisticated exploit — scanning port 22 is enough.
The references also point to discussions around Coolify and a Docker sshd image, a sign that the issue reaches hosting tools and containers, not just hand-built Alpine servers.
Affected versions
| NVD configuration | Status |
|---|---|
| OpenSSH before 10.6 | affected |
| OpenSSH 10.6 and 10.6p1 | affected |
| OpenSSH 10.6p2 | fixed (per the NVD description and the OpenSSH release notes) |
⚠️ These bounds refer to upstream OpenSSH portable. On Alpine and other distributions, the fix may ship under a distro-specific package version: check the Alpine Linux announcement of November 5 listed in the references, and your distribution's advisories.
Check the version and libc:
ssh -V
ldd --version 2>&1 | head -1
cat /etc/os-release
And the effective sshd configuration:
sshd -T | grep -Ei 'passwordauthentication|usepam'
Who is actually exposed
- Alpine containers running
sshdwith password authentication — common for "bastion" containers, SFTP servers and dev environments. - Appliances and embedded systems built on musl.
- Mainstream glibc servers (Debian, Ubuntu, RHEL) do not match the "musl" condition NVD describes. That is no reason to skip the update, but it is not where the urgency lies.
The tricky part: containers don't get inventoried like servers. An image built six months ago with apk add openssh keeps running that version until someone rebuilds it.
Detection
- Successful password logins on accounts that never use passwords:
grep "Accepted password" /var/log/messages(or the container's log) - New keys in
~/.ssh/authorized_keys, new accounts, recent cron jobs - Port 22 scans from IPs already flagged by reputation feeds
Mitigation
1. Move to OpenSSH 10.6p2 or your distribution's fixed package
Then rebuild the images that ship sshd: patching the host does not patch the containers.
2. In the meantime, turn off password authentication
PasswordAuthentication no
KbdInteractiveAuthentication no
Public key authentication is not covered by the NVD description. Restart sshd and confirm with sshd -T.
3. Keep SSH off the Internet
Source IP filtering, a VPN or a bastion host. An SSH container published on 0.0.0.0:22 is exactly what this flaw targets.
4. If a container was exposed
CISA requires forensic triage (BOD 26-04) on top of the update. Treat the container as compromised: collect its logs, replace it with a rebuilt image, and rotate every secret it held.
Why continuous monitoring of your OpenSSH versions matters
OpenSSH runs everywhere and gets updated rarely, especially inside container images. A flaw that only hits one libc-plus-configuration combination can only be spotted if you know exactly what runs where.
With cveo.tech, inventory your servers, appliances and images with their versions, and get an alert as soon as a CVE affecting them lands in the CISA KEV catalog.