The US Cybersecurity and Infrastructure Security Agency (CISA) has added four vulnerabilities to its Known Exploited Vulnerabilities (KEV) catalog, including an OpenSSH flaw that can let an attacker log in to some Linux servers without a valid password.

In an alert dated 9 November 2026, CISA said the additions were made "based on evidence of active exploitation". Its catalog describes CVE-2026-123158 as an issue in which "OpenBSD OpenSSH on Linux contains an unexpected status code or return value vulnerability that could allow for authentication bypass." The entry lists the weakness as CWE-394, a due date of 12 November 2026, forensic triage as required, and known ransomware use as "Unknown".

“These types of vulnerabilities are a frequent attack vector for malicious cyber actors and pose significant risks to the federal enterprise.”

CISA alert, 9 November 2026

Background

The OpenSSH project released portable OpenSSH 10.6p2 on 5 November 2026 with what it called "a critical security workaround that affects Linux systems that use the musl libc and PAM disabled." The release notes describe a change to sshd to "avoid password authentication bypass that is exploitable through sshd(8) that affects some Linux systems when built and run with PAM support disabled", and add: "We consider the root cause of this bug to be outside sshd, but it is exploitable via sshd and can be avoided there." OpenSSH credits Özgün Kültekin of Wakefield with the report. CISA's catalog entry links to the release notes, the Alpine advisory and the upstream fix.

Alpine Linux, which uses musl, published an advisory the same day. It explains that when sshd is built without PAM it checks passwords with the C library's crypt() function. musl's crypt() returns * as an error for keys longer than 256 bytes, and * is also what the password field contains for accounts with no password set, so the comparison can succeed. Alpine says an attacker who can reach the SSH port needs the name of such an account, and that at least one other account on the machine must have a $5$ or $6$ password hash.

Alpine says every release it checked is affected, from 3.16 through 3.24 and edge, and that it has published fixed packages back to 3.16. It lists Alpine 3.21.10, 3.22.8, 3.23.8 and 3.24.4 as containing the fix. Systems using openssh-server-pam with UsePAM yes, or with PasswordAuthentication no, are not affected, according to the advisory. At the time Alpine published, it said no CVE identifier had been assigned; CISA's catalog now tracks the flaw as CVE-2026-123158.

Reports of attacks

CISA does not say who is exploiting the flaw. Security firms have described attacks publicly: BleepingComputer, citing the threat intelligence company GreyNoise, reported that the first successful exploitation in the wild was recorded on 7 November at 00:46 UTC, about 40 hours after the fix was released. The Hacker News and BleepingComputer both refer to the bug by the nickname "SSHole".

The other three additions

CISA's 9 November alert also added CVE-2026-102895, an improper authentication flaw in the GPUStack AI model-serving platform that its catalog says could allow unauthenticated administrative access and code execution; CVE-2026-116779, a code injection flaw in SignalWire FreeSWITCH that permits credential disclosure, arbitrary call control and command execution; and CVE-2026-123218, an incorrect authorisation flaw in IBM Aspera Faspex that could let an authenticated user escalate privileges. All four entries carry the same 12 November due date.

That date applies to US Federal Civilian Executive Branch agencies under Binding Operational Directive (BOD) 26-04. CISA says that while the directive applies only to those agencies, it "encourages all organizations to adopt risk-based vulnerability management and prioritize remediation of KEV Catalog vulnerabilities."

What administrators should do

Alpine's advice is to run apk upgrade -U -a and then restart sshd, because "Upgrading the package alone does not replace the running daemon." If an update is not yet possible, it recommends setting PasswordAuthentication no. To look for past abuse, it suggests checking /var/log/messages for "Accepted password for" entries on accounts that have no password, and reviewing doas use, new users and authorised keys.

What this means for server owners

Analysis by Depakar B

The conditions OpenSSH and Alpine describe are narrow: musl libc, PAM disabled and password logins switched on. Servers outside that set are not exposed to this particular bug. But for any machine that does match, CISA's exploitation listing means it should be treated as urgent rather than routine maintenance.

The safest move is to use key-only SSH logins. Password authentication on an internet-facing server is rarely needed, and turning it off closes this hole and a whole class of brute-force attacks. If you look after servers for clients, check any Alpine-based images today and restart sshd after patching.

About this report

Based on CISA's alert and KEV catalog entry, the OpenSSH 10.6p2 release notes and the Alpine Linux security advisory. Facts and quotes are taken from the sources credited below, which I read on 10 November 2026 and checked again on 11 November 2026 against the coverage listed below. Sections marked "Analysis" are my own view. I am an independent developer and am not affiliated with the organisations named here.

Credits and sources

Corrections

Spotted an error? Please contact me. Corrections are noted on this page with the date.