{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-126641 in the wild and no public exploit code.","exposure":"An affected version is only exploitable if your software calls Session.verify_knownhost() or AutoAddPolicy. Many projects that include it are not exposed.","fix":"No fix has been published for CVE-2026-126641 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-126641 is a medium-severity security feature bypass vulnerability in Red Hat Ansible Automation Platform 2, published on 12 Nov 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-126641 and fix it if it is affected.\n\nWhat it is: CVE-2026-126641 is a medium-severity security feature bypass vulnerability in Red Hat Ansible Automation Platform 2, published on 12 Nov 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-126641 in the wild and no public exploit code.\nExposure: An affected version is only exploitable if your software calls Session.verify_knownhost() or AutoAddPolicy. Many projects that include it are not exposed.\n\nAffected product: Red Hat Ansible Automation Platform 2. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n   If an affected version is present, also search the code for calls to Session.verify_knownhost() or AutoAddPolicy and report whether any exist.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-126641/ (Markdown: https://insights.sbomify.com/CVE-2026-126641/index.md)","id":"CVE-2026-126641","markdown":"https://insights.sbomify.com/CVE-2026-126641/index.md","name":"CVE-2026-126641","record":{"aliases":["GHSA-qvc6-2r95-pxqv"],"analysis":{"component_type":"library","exploitable_when_present":false,"fix_type":"no_fix_stated","impacts":["security_bypass","data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"Ansible SSH library","requires_auth":"none","requires_specific_call":true,"summary":"A machine-in-the-middle attacker can impersonate hosts to Ansible when host_key_auto_add is enabled, since changed host keys are accepted without warning.","user_interaction":"not_required","vuln_class":"security_feature_bypass","vulnerable_functions":["Session.verify_knownhost()","AutoAddPolicy"]},"analysis_generated_by":"sbomify/insights-2b-fp8","assigner":"redhat","cpe":[],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-322","name":"Key Exchange without Entity Authentication"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Ansible-pylibssh: accepts a changed ssh host key when host_key_auto_add is enabled","id":"CVE-2026-126641","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Awx: webhook credential assignment omits use_role check, exposing another user's token","id":"CVE-2026-126642"},"nickname":null,"packages":[],"prev":{"headline":"Apache XML Graphics FOP: Temporary files on Unix-like systems are readable by other local users","id":"CVE-2026-126627"},"products":["Red Hat Ansible Automation Platform 2"],"published":"2026-11-12","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-11-12","vendors":["Red Hat"]},"summary":"A machine-in-the-middle attacker can impersonate hosts to Ansible when host_key_auto_add is enabled, since changed host keys are accepted without warning.","url":"https://insights.sbomify.com/CVE-2026-126641/"}