Red Hat Ansible Automation Platform 2 ansible-core meta/requirements.yml src argument injection

Summaryinfo

A vulnerability classified as critical has been found in Red Hat Ansible Automation Platform 2. Affected by this vulnerability is an unknown functionality of the file meta/requirements.yml of the component ansible-core. The manipulation of the argument src leads to argument injection. This vulnerability is referenced as CVE-2026-11332. The attack can only be performed from a local environment. No exploit is available.

Detailsinfo

A vulnerability, which was classified as critical, has been found in Red Hat Ansible Automation Platform 2. This issue affects some unknown processing of the file meta/requirements.yml of the component ansible-core. The manipulation of the argument src with an unknown input leads to a argument injection vulnerability. Using CWE to declare the problem leads to CWE-88. The product constructs a string for a command to be executed by a separate component in another control sphere, but it does not properly delimit the intended arguments, options, or switches within that command string. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

A flaw was found in ansible-core. The ansible-galaxy role install command processes dependency specifications from a role's meta/requirements.yml file. Due to improper neutralization of argument delimiters, a malicious role author can inject arbitrary git configuration flags through the src field. This allows arbitrary code execution on the machine of a user who installs the role via ansible-galaxy role install.

The advisory is shared at access.redhat.com. The identification of this vulnerability is CVE-2026-11332 since 06/05/2026. The exploitation is known to be easy. An attack has to be approached locally. Technical details are known, but no exploit is available. The price for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 06/05/2026). MITRE ATT&CK project uses the attack technique T1059 for this issue.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

• Automation Software

Vendor

• Red Hat

Name

• Ansible Automation Platform

Version

• 2

License

• open-source

Website

• Vendor: https://www.redhat.com/

CPE 2.3info

• 🔒

CPE 2.2info

• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion