Live › vulnerability › CVE-2026-94423
Go to dashboardNet::LibSSH before 0.004 for Perl never checks the server's host key against known_hosts, so the strict_hostkeycheck and knownhosts options have no effect. An attacker who can redirect the connection gets the password, commands and data sent over the session.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Perl applications that use Net::LibSSH to open SSH connections to servers, especially where the connection target could be redirected by DNS, routing or a network an attacker controls. Scripts that only connect to hosts on a fully trusted, isolated network carry less risk, but the upgrade is still the fix.
No product ranges from the sources yet.
cpanm --info Net::LibSSH or perl -MNet::LibSSH -e 'print $Net::LibSSH::VERSION' and look for a version below 0.004Net::LibSSH0.004 or laterEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
Net::LibSSH versions before 0.004 for Perl authenticate to an unverified server because connect never checks the host key against known_hosts.
connect reports success as soon as ssh_connect returns SSH_OK. libssh leaves the known-hosts check to the application, and this binding never makes it, so the strict_hostkeycheck and knownhosts options are set on the session and then decide nothing.
Password, agent and public-key authentication, channel and SFTP operations all run on a session whose peer was never identified, so an attacker who can redirect the connection receives the password when password authentication is used, and commands and data sent over the session.
This page as .md · .json · in your agent: get_signal("CVE-2026-94423")
NVD data is provided by NIST and is public domain · EPSS scores by FIRST, used with attribution. Posts quoted belong to their authors.