Read the docs

Ansible-pylibssh accepts changed SSH host keys with auto-add enabled

Priority LOW 29CWE-322Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
High
Impact type
—
Confidentiality · integrity · availability
High · Low · None
Fix status
Deferred Red Hat: fix deferred

Attack profile from CVSS 3.1 · CNA. Fix status from CNA and Red Hat.

Summary

Ansible-pylibssh and the ansible.netcommon libssh connection plugin accept a changed SSH host key when trust-on-first-use is enabled. A host already in known_hosts is accepted with a different key without warning (CWE-322). A machine-in-the-middle attacker can receive connection credentials, since the controller runs the play on the substitute host. Default configurations are not affected.

Written with Claude Haiku 5.5 from the sources below · 2026-11-12

Description from the CNA

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.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00333 26th percentileScored 2026-11-16
Fix Deferred Red Hat: fix deferred

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
Red HatRed Hat Ansible Automation Platform 2——No fix listedCNA
Red HatRed Hat Ansible Automation Platform 2——No fix listedCNA
Red HatRed Hat Ansible Automation Platform 2——No fix listedCNA
Red HatRed Hat Ansible Automation Platform 2——No fix listedCNA
Red HatRed Hat Ansible Automation Platform 2——No fix listedCNA
Red HatRed Hat Ansible Automation Platform 2——No fix listedCNA
  • Red Hat Ansible Automation Platform 2 VendorRed Hat Affected — Fixed in — No fix listed CNA
  • Red Hat Ansible Automation Platform 2 VendorRed Hat Affected — Fixed in — No fix listed CNA
  • Red Hat Ansible Automation Platform 2 VendorRed Hat Affected — Fixed in — No fix listed CNA
  • Red Hat Ansible Automation Platform 2 VendorRed Hat Affected — Fixed in — No fix listed CNA
  • Red Hat Ansible Automation Platform 2 VendorRed Hat Affected — Fixed in — No fix listed CNA
  • Red Hat Ansible Automation Platform 2 VendorRed Hat Affected — Fixed in — No fix listed CNA

CPE names CNA · 1

CPEVersionsRoleVendor
cpe:/a:redhat:ansible_automation_platform:22—Red Hat
  • cpe:/a:redhat:ansible_automation_platform:2 Versions 2 — ·Red Hat

Remediation

The sources list no fixed version for Red Hat Ansible Automation Platform 2, and Red Hat states no fix plan is available for it. Keep host_key_auto_add unset, since default configurations are not affected.

Written with Claude Haiku 5.5 from the sources below · 2026-11-12

Vendor assessments

Red Hat

Red Hat rating: Moderate. Red Hat's page for this CVE →

ProductStatusPlan or fix
Red Hat Ansible Automation Platform 2AffectedNo fix yet: Fix deferred

Timeline

  1. 2026-11-12 Threatist record created from CVE-2026-126641
  2. 2026-11-12 Alias added: GHSA-qvc6-2r95-pxqv
  3. 2026-11-12 Affected versions changed · Red Hat
  4. 2026-11-12 CVSS score added · Red Hat
  5. 2026-11-13 CISA SSVC decision points changed

References

  • TI-2019-15875 Sandbox bypass in Jenkins Pipeline: Groovy Plugin runs code KEVCVSS 3.1CRITICAL 9.9
  • TI-2019-15874 Sandbox bypass in Jenkins Script Security Plugin allows code execution KEVCVSS 3.1CRITICAL 9.9
  • TI-2019-08259 Buffer underflow in PHP-FPM allows remote code execution KEVCVSS 3.1CRITICAL 9.8
  • TI-2019-05363 Arbitrary code execution in Kibana Timelion visualizer KEVCVSS 3.1CRITICAL 10.0
  • TI-2019-03949 Out-of-bounds write in OpenSLP in VMware ESXi and Horizon DaaS KEVCVSS 3.1CRITICAL 9.8
  • TI-2018-16080 Jenkins Stapler Framework Code Execution via Crafted URLs KEVCVSS 3.1CRITICAL 9.8
See all 7494 →

Sources