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


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 21 Oct 2026
- **Updated:** 22 Oct 2026
- **Also known as:** GHSA-5q49-7p5p-mjwf

## What is CVE-2026-94423?

CVE-2026-94423 is a vulnerability, published on 21 Oct 2026. 

### Official 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.

Weakness: CWE-322 (Key Exchange without Entity Authentication)

## Which versions are affected by CVE-2026-94423?


## How do I fix CVE-2026-94423?

No fix has been published for CVE-2026-94423 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-94423 being exploited?

There is no known exploitation of CVE-2026-94423 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-94423 and fix it if it is affected.

What it is: CVE-2026-94423 is a vulnerability, published on 21 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-94423 in the wild and no public exploit code.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-94423/ (Markdown: https://insights.sbomify.com/CVE-2026-94423/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-94423
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-94423
- OSV: https://osv.dev/vulnerability/CVE-2026-94423

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-94423/
Summaries are generated and may contain mistakes; the official description above is the record.