CVE-2026-11332 is a high-severity (CVSS 7.8) CWE-88 vulnerability in ansible-core. O3 Security confirms whether CVE-2026-11332 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
ansible-core: Argument injection in ansible-galaxy role install leads to arbitrary code execution
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.19rc1 |
| 🐍PyPI | ansible-core | ≥ 2.17.0b1&&< 2.18.18rc1 | 2.18.18rc1 |
| 🐍PyPI | ansible-core | ≥ 2.19.0b1&&< 2.19.11rc1 | 2.19.11rc1 |
| 🐍PyPI | ansible-core | ≥ 2.20.0b1&&< 2.20.7rc1 | 2.20.7rc1 |
| 🐍PyPI | ansible-core | ≥ 2.21.0b1&&< 2.21.1rc1 | 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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
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.
How O3 protects you
O3 pinpoints whether CVE-2026-11332 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to CVE-2026-11332. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2026-11332 in your dependencies?
O3 detects CVE-2026-11332 across PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.