We are not a hacking tool.
That is why you must register and verify that you own a site before we will run any vulnerability scans on it. Sorry for the inconvenience, but we have to be a responsible member of the community.
How this scan works, and every vulnerability it checks for →
SSH Password Bypass Check
Check an SSH server of a verified site for the conditions of CVE-2026-123158, the OpenSSH password authentication bypass: version banner and offered authentication methods. Sends no password.
One connection: the SSH version exchange, the key exchange and one authentication request of the method “none” for the user nettests-check. No password is sent, keyboard-interactive login is not tried and no session is opened.
About CVE-2026-123158
CVE-2026-123158 lets sshd accept a wrong password for some accounts. It concerns Portable OpenSSH before 10.6p2 on Linux, built with musl libc and without PAM (or with PAM support and UsePAM no), with password authentication enabled. Builds against glibc (Debian, Ubuntu, Red Hat, Fedora), builds that use PAM, the OpenBSD sshd and systems other than Linux are not affected. In practice the affected builds are Alpine Linux (edge and 3.16 to 3.24) and Alpine-based containers with an openssh package older than the fixed package of their branch.
CVSS 8.1 (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H). In the CISA Known Exploited Vulnerabilities catalogue since 2026-11-09; remediation due 2026-11-12. Fixed in OpenSSH 10.6p2 (2026-11-05).
Monitor SSH Password Bypass Check automatically
Check an SSH server of a verified site for the conditions of CVE-2026-123158, the OpenSSH password authentication bypass: version banner and offered authentication methods. Sends no password. NetTests can run this check on a schedule, preserve historical results, compare changes over time, and alert you the moment something breaks.
Start monitoring free → See all monitoring productsFrequently Asked Questions
What does the SSH Password Bypass Check send to my server?
One connection to the SSH port (22 by default): the SSH version exchange, the key exchange and one authentication request of the method “none” for the user nettests-check. The server refuses that request and lists the authentication methods it offers. The check then closes the connection. It never sends a password, never tries keyboard-interactive login and never opens a session.
Why is the result “possibly affected” and not a confirmed finding for CVE-2026-123158?
CVE-2026-123158 requires a build against musl libc without PAM. The SSH banner shows the OpenSSH version but not the C library, the PAM setting or a distribution's backported fix: a patched Alpine package openssh 10.3_p1-r2 still announces OpenSSH_10.3p1. Confirming the flaw would require sending passwords, which this check does not do. The result names the commands that settle the question on the server.
Why does the check run only with “I control this whole server”?
On shared hosting the SSH server belongs to the hosting provider and serves every account on the machine. The check connects to it only when you tick the option; without it no connection is made and the result states that the check was not run. The check also runs only against sites whose ownership your account has verified.