CVE-2026-11332

ansible-core: Argument injection in ansible-galaxy role install leads to arbitrary code execution

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.

CVE-2026-11332 has a CVSS score of 7.8 (High). The vector is requires local access, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.16.19rc1, 2.18.18rc1, 2.19.11rc1, 2.20.7rc1, 2.21.1rc1); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

1. What is CVE-2026-11332? CVE-2026-11332 is a high-severity security vulnerability in ansible-core (pip), affecting versions < 2.16.19rc1. It is fixed in 2.16.19rc1, 2.18.18rc1, 2.19.11rc1, 2.20.7rc1, 2.21.1rc1.
2. How severe is CVE-2026-11332? CVE-2026-11332 has a CVSS score of 7.8 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of ansible-core are affected by CVE-2026-11332? ansible-core (pip) versions < 2.16.19rc1 is affected.
4. Is there a fix for CVE-2026-11332? Yes. CVE-2026-11332 is fixed in 2.16.19rc1, 2.18.18rc1, 2.19.11rc1, 2.20.7rc1, 2.21.1rc1. Upgrade to this version or later.
5. Is CVE-2026-11332 exploitable, and should I be worried? Whether CVE-2026-11332 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-11332 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-11332?
   • Upgrade ansible-core to 2.16.19rc1 or later
   • Upgrade ansible-core to 2.18.18rc1 or later
   • Upgrade ansible-core to 2.19.11rc1 or later
   • Upgrade ansible-core to 2.20.7rc1 or later
   • Upgrade ansible-core to 2.21.1rc1 or later

Other vulnerabilities in ansible-core