CVE-2026-11332 is a high-severity (CVSS 7.8) CWE-88 vulnerability in ansible-core. A fix is available for ansible-core — see the affected versions and patch details below.
ansible-core: Argument injection in ansible-galaxy role install leads to arbitrary code execution
Exploitation Status
No confirmed exploitation observed yet
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-11332.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2026-11332 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 379,842 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
ansible-core🐍ansible-core🐍ansible-core🐍ansible-core🐍ansible-coreReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.
Description
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | ansible-core | all versions | 2.16.19rc1pip install --upgrade 'ansible-core==2.16.19rc1' |
| 🐍PyPI | ansible-core | ≥ 2.17.0b1&&< 2.18.18rc1 | 2.18.18rc1pip install --upgrade 'ansible-core==2.18.18rc1' |
| 🐍PyPI | ansible-core | ≥ 2.19.0b1&&< 2.19.11rc1 | 2.19.11rc1pip install --upgrade 'ansible-core==2.19.11rc1' |
| 🐍PyPI | ansible-core | ≥ 2.20.0b1&&< 2.20.7rc1 | 2.20.7rc1pip install --upgrade 'ansible-core==2.20.7rc1' |
| 🐍PyPI | ansible-core | ≥ 2.21.0b1&&< 2.21.1rc1 | 2.21.1rc1pip install --upgrade 'ansible-core==2.21.1rc1' |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ansible-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update ansible-core to 2.16.19rc1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-11332 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
Conditions for Exploitation: Successful exploitation requires user interaction, specifically tricking a victim into installing a maliciously crafted Ansible role (or a role with a malicious dependency) using the ansible-galaxy role install command. Broad Impact: While user interaction is required, the potential impact…
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.Source: Red Hat security advisory for CVE-2026-11332 (CC BY 4.0)
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat Ansible Automation Platform 2.5 for RHEL 8 | ansible-core-1:2.16.19-1.el8ap | RHSA-2026:42078 |
| Red Hat Ansible Automation Platform 2.6 for RHEL 10 | ansible-core-2:2.16.19-1.el10ap | RHSA-2026:42079 |
| Red Hat Ansible Automation Platform 2.7 for RHEL 10 | ansible-core-2:2.16.19-1.el10ap | RHSA-2026:42080 |
| Red Hat Enterprise Linux 10 | ansible-core-1:2.16.16-2.el10_2.1 | RHSA-2026:57148 |
| Red Hat Enterprise Linux 10.0 Extended Update Support | ansible-core-1:2.16.14-1.el10_0.1 | RHSA-2026:67465 |
| Red Hat Enterprise Linux 8 | ansible-core-0:2.16.3-4.el8_10 | RHSA-2026:66248 |
| Red Hat Enterprise Linux 9 | ansible-core-1:2.14.18-3.el9_8.1 | RHSA-2026:57149 |
| Red Hat Enterprise Linux 9.4 Update Services for SAP Solutions | ansible-core-1:2.14.14-1.el9_4.1 | RHSA-2026:67467 |
Frequently Asked Questions
Is CVE-2026-11332 in your dependencies?
Find it across PyPI, including transitive dependencies.