The SSH Password Bypass Check reads the version banner and the offered authentication methods of the SSH server of a verified site and compares them with the conditions of CVE-2026-123158. CVE-2026-123158 lets sshd accept a wrong password for some accounts in Portable OpenSSH before 10.6p2 on Linux, built with musl libc and without PAM (or with UsePAM no), with password authentication enabled. The check runs on demand and in scheduled reports, only against sites whose ownership your account has verified, and only with the option “I control this whole server”. It never sends a password.
How it tests
- One TCP connection to the SSH port you give (22 by default; 1 to 65535; the mail ports 25, 465 and 587 are refused). Your host name is resolved first; a host that resolves only to non-public addresses ends the check with that error.
- On that connection: the SSH version exchange, the key exchange, and one authentication request of the method “none” for the user
nettests-check. The server refuses the request and lists the authentication methods it offers. The connection is then closed. - No password is sent, keyboard-interactive login is not tried and no session is opened. A server that accepts the method “none” is reported as a warning and the connection is closed at once.
- With the option “I control this whole server” off (the default), no connection is made: on shared hosting the SSH server belongs to the hosting provider and serves every account on the server. A report saved without the option runs with it off.
- The verdict is read from the banner and the method list, in this order:
1. The server accepted the method “none” (it admitted the unknown user without a password or a key): warning, whatever the banner says.
2. The banner does not name OpenSSH: not affected.
3. OpenSSH for Windows: not affected (not Linux).
4. A version without a portable release number (
OpenSSH_10.6,OpenSSH_7.4, nop1,p2): not affected. This is the OpenBSD sshd or a distribution build that removes the suffix (Red Hat, FreeBSD, NetBSD), none of which is a musl build named in the advisory. When the banner's comment names FreeBSD or NetBSD (OpenSSH_9.6 FreeBSD-20240104), the result gives that reason: not Linux. 5. Portable OpenSSH 10.6p2 or later: not affected (fixed release). 6. The banner's comment names Debian, Ubuntu or Raspbian (builds against glibc), or FreeBSD or NetBSD (not Linux): not affected. 7. Otherwise, password authentication not among the offered methods: not exposed. 8. Otherwise: possibly affected.
What you see
| Situation | Result |
|---|---|
| Not OpenSSH, OpenSSH for Windows, no portable release number (OpenBSD sshd, Red Hat, FreeBSD, NetBSD), 10.6p2 or later, Debian, Ubuntu, Raspbian, FreeBSD or NetBSD build | Passed: “Not affected”, with the reason |
| Portable OpenSSH before 10.6p2, password authentication not offered | Passed: “Not exposed: the server does not offer password authentication”, with the note that enabling password authentication later exposes a build against musl libc without PAM |
| Portable OpenSSH before 10.6p2, password authentication offered | Warning: “Possibly affected by CVE-2026-123158”, with the steps below |
| The server accepted the method “none” for the unknown user | Warning: “the server admitted an unknown user without credentials”, with the sshd_config settings to check; CVE-2026-123158 is not judged |
| Option “I control this whole server” off | Not checked: no connection was made, and why |
| Connection or protocol error, no banner, a banner without a software version, or the method list could not be read | Not checked, with the error; never a pass. A banner the server sent before the error is kept |
| In a scheduled report | “Possibly affected”, the “none” warning and “Not checked” set the run to warning, without a threshold; “Passed” sets it to OK |
The steps for a possibly affected server: run apk info openssh (Alpine Linux and Alpine-based containers) and compare the installed version with the fixed package of its branch (edge 10.6_p2-r0, 3.24 10.3_p1-r2; Alpine Linux 3.21.10, 3.22.8, 3.23.8 and 3.24.4 ship the fixed package; the Alpine advisory lists the fixed package of every other branch). If it is older, run apk upgrade openssh and restart sshd. Alternatively, or until the upgrade, set PasswordAuthentication no and restart sshd.
Limits
- The banner does not show the C library of the build, the PAM setting or a distribution's backported fix. A patched Alpine package keeps the old upstream version in its banner (
10.3_p1-r2still announcesOpenSSH_10.3p1), so the check cannot prove a server affected; its worst result is “possibly affected”. - Confirming the flaw would require sending passwords. The check does not do that.
- A server that hides or rewrites its version banner is judged by what it announces.
- The method list is the one the server gives for the user
nettests-check; a server configured per user (aMatch Userblock) can offer other methods to other accounts.