Technical impact
The vulnerability arises from ansible-core's handling of the role name field during ansible-galaxy role installation. The supplied name is concatenated to form the on‑disk installation path without verifying that the resulting path remains inside the configured roles directory. If the name contains two dots and a slash it can escape the intended directory, and if it is an absolute path it can overwrite or replace arbitrary locations on the filesystem. An attacker who controls a role’s meta requirements yaml can thus inject files or, when ansible-galaxy is invoked with force, delete a directory outside the roles path. The impact is limited to the privileges of the operator performing the install, but it can lead to privilege escalation or malicious code execution if the operator has elevated rights.
Affected Systems
The affected products span many of Red Hat’s automation and platform offerings. Red Hat Ansible Automation Platform (v2), Ansible Core (v2), and all roles and collections managed through this platform are vulnerable. The issue also affects Red Hat Advanced Cluster Management for Kubernetes (v2), Red Hat OpenShift Service Mesh (v3), the Red Hat OpenShift Container Platform (v4 and v5), OpenStack Platform (v17.1 and v18.0), the Red Hat Migration Toolkit for Applications (v8) and Migration Toolkit for Virtualization (v2), as well as the Enterprise Linux 8/9/10 systems that host these tools. Red Hat Enterprise Linux 8 and 9, along with related Discovery, Satellite, and Certification tools, are also affected via the underlying Ansible components.
Risk and Exploitability
The CVSS score of 8.1 classifies this as high severity. Because the exploit requires a privileged operator to install a malicious role, the likelihood of widespread exploitation is moderate, and the EPSS data is currently unavailable, which suggests it has not been widely observed in the wild. The vulnerability is not listed in CISA’s KEV catalog, but the risk remains significant for organizations that routinely install roles from external sources. The attack vector is local to the operator executing ansible-galaxy, but an untrusted role repository can indirectly expose the system to attackers if the role is installed.