CVE & CISA-KEV Catalog

CVE-2026-126641

MEDIUM
6.5
CVSS v3
NVD

Description

A host key verification flaw was found in ansible-pylibssh and in the ansible.netcommon libssh connection plugin. When trust-on-first-use is enabled (host_key_auto_add on the libssh connection plugin, or AutoAddPolicy in ansible-pylibssh), a host that is already present in known_hosts but now presents a different key is accepted without warning. The pylibssh Session.verify_knownhost() method passes the SSH_KNOWN_HOSTS_CHANGED and SSH_KNOWN_HOSTS_OTHER states to the same missing_host_key() policy hook used for unknown hosts, and the bundled AutoAddPolicy/RejectPolicy classes (as well as ansible.netcommon's MyAddPolicy, which is modeled on paramiko's AutoAddPolicy) therefore add the changed key and continue the connection rather than aborting as paramiko's BadHostKeyException path would. As a result the controller authenticates to the substitute host, runs the play there, and appends the new key to known_hosts, which can disclose connection credentials to an attacker performing a machine-in-the-middle attack. Default configurations (host_key_checking enabled, host_key_auto_add unset) are not affected; non-interactive runs fail closed.

How to fix

No published remediation has been found for this vulnerability's affected products yet.

Mitigation guidance may be in the linked vendor advisories in the References section below.

TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works

CVSS v3 Vector

Exploitability

Attack VectorNetwork
Attack ComplexityHigh
Privileges RequiredNone
User InteractionNone
ScopeUnchanged

Impact

ConfidentialityHigh
IntegrityLow
AvailabilityNone

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N

Exploit Intelligence

0.33%probability of exploitation in 30 days
27thpercentile

Low risk: more likely to be exploited than 27% of all known CVEs.

References

Related Vulnerabilities

Other CWE-322 vulnerabilities, ordered by exploit likelihood. View all

CVESeverityCVSSEPSSExploitedFix
CVE-2026-1709Critical9.45.7%-Fix
CVE-2022-39249High7.51.3%-Fix
CVE-2022-39250High8.61.2%-Fix
CVE-2022-39251High8.61.2%-Fix
CVE-2022-39255High8.61.0%-Fix
CVE-2022-39257High7.51.0%-Fix

Common questions

How do I fix CVE-2026-126641?

No published fix for CVE-2026-126641 has been found yet. Check the linked vendor advisories for guidance as it becomes available.

Is CVE-2026-126641 being actively exploited?

Not that we know of. CVE-2026-126641 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.33% is the estimated probability that it will be exploited in the next 30 days. That is higher than 27% of all scored CVEs.

How severe is CVE-2026-126641?

CVE-2026-126641 has a CVSS v3 base score of 6.5, rated medium. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.

Embed a live status badge for CVE-2026-126641
CVE-2026-126641 severity badge

Markdown

[![CVE-2026-126641](https://tridentstack.com/cve/badge/CVE-2026-126641.svg)](https://tridentstack.com/cve/CVE-2026-126641)

HTML

<a href="https://tridentstack.com/cve/CVE-2026-126641"><img src="https://tridentstack.com/cve/badge/CVE-2026-126641.svg" alt="CVE-2026-126641"></a>

Find and fix vulnerabilities across your fleet

TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.

Run a free CVE scan on your fleetStart freeThis CVE lookup is free and always will be.

This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-11-13.