CVE-2026-105929: ansible-core's ansible-galaxy role installation · Path Traversal Vulnerability Was Found
Source GCVE Database
Not known to be exploited · CVSS 8.1 High.
Data as of 18 Nov 2026, 05:21 UTC
Thin evidence
One scorer or none| CNA (redhat) | CVSS 3.1 | 8.1 |
|---|
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 18 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 17 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Migration Toolkit for Applications 8mta/mta-rhel9-operator | Affected– | Fixed in– |
| Migration Toolkit for Virtualizationmigration-toolkit-virtualization/mtv-rhel9-operator | Affected– | Fixed in– |
| OpenShift Service Mesh 3openshift-service-mesh/kiali-rhel9-operator | Affected– | Fixed in– |
| Red Hat Advanced Cluster Management for Kubernetes 2rhacm2/volsync-operator-bundle | Affected– | Fixed in– |
| Red Hat Advanced Cluster Management for Kubernetes 2rhacm2/volsync-rhel9 | Affected– | Fixed in– |
| Red Hat Ansible Automation Platform 2ansible-automation-platform-24/de-minimal-rhel8 | Affected– | Fixed in– |
AI-suggested
Install roles and collections only from trusted sources. Before installing a role, review its meta/requirements.yml file and any transitive dependencies for 'name' values containing '../' or absolute paths. Avoid using 'ansible-galaxy role install --force' on untrusted content.
Description
A path traversal vulnerability (CWE-22) exists in ansible-core's ansible-galaxy role installation process. The vulnerability arises because the role name from meta/requirements.yml is used to construct the installation path without proper validation, allowing directory escape via '../' or absolute paths. This can lead to attacker-controlled files being written outside the intended roles directory and, with the use of the --force option, existing directories outside the roles path can be deleted and replaced. The impact depends on the invoking user's filesystem permissions and requires the operator to install the malicious role.