CVE-2026-126641: A host key verification flaw was found in ansible-pylibssh and in the ansible.netcommon libssh
Source GCVE Database
Not known to be exploited · CVSS 6.5 Medium.
Data as of 12 Nov 2026, 13:35 UTC
Thin evidence
One scorer or none| CNA (redhat) | CVSS 3.1 | 6.5 |
|---|
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 12 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 12 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Red Hat Ansible Automation Platform 2ansible-automation-platform-26/ee-supported-rhel9 | Affected– | Fixed in– |
| Red Hat Ansible Automation Platform 2ansible-automation-platform-27/ee-supported-rhel9 | Affected– | Fixed in– |
| Red Hat Ansible Automation Platform 2python3.11-ansible-pylibssh | Affected– | Fixed in– |
| Red Hat Ansible Automation Platform 2python3.12-ansible-pylibssh | Affected– | Fixed in– |
| Red Hat Ansible Automation Platform 2python3x-ansible-pylibssh | Affected– | Fixed in– |
| Red Hat Ansible Automation Platform 2python-ansible-pylibssh | Affected– | Fixed in– |
AI-suggested
Do not enable host_key_auto_add in the ansible.netcommon libssh connection plugin or AutoAddPolicy in ansible-pylibssh. Keep host_key_checking enabled and pre-populate known_hosts with verified host keys to ensure that changed keys cause the connection to fail closed. Default configurations are not affected, so maintaining default settings mitigates this vulnerability.
Description
A host key verification flaw exists in ansible-pylibssh and the ansible.netcommon libssh connection plugin when trust-on-first-use is enabled. If a host's SSH key changes but is already present in known_hosts, the changed key is accepted without warning, allowing a man-in-the-middle attacker to impersonate the host and potentially capture credentials. Default configurations with host key checking enabled and trust-on-first-use disabled are not affected, and non-interactive runs fail closed.