# CVE-2026-11332: Ansible-core: argument injection in ansible-galaxy role install leads to arbitrary code execution > A malicious Ansible role can inject git flags via requirements.yml, leading to arbitrary code execution on the user's machine during installation. - **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Local or same network only - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 5 Jun 2026 - **Updated:** 21 Oct 2026 - **Also known as:** ALSA-2026:57148, ALSA-2026:57149, ALSA-2026:66248, AZL-89402, CLSA-2026-1788175790, CLSA-2026-1788269423, DEBIAN-CVE-2026-11332, GHSA-w8p5-mx5w-cpqj, PYSEC-2026-3458, RHSA-2026:57148, RHSA-2026:57149, RHSA-2026:66248, RHSA-2026:67465, RHSA-2026:67466, RHSA-2026:67467, RLSA-2026:57148, RLSA-2026:57149, RLSA-2026:66248, SUSE-SU-2026:22171-1, SUSE-SU-2026:2680-1, UBUNTU-CVE-2026-11332, openSUSE-SU-2026:11007-1, openSUSE-SU-2026:11062-1, openSUSE-SU-2026:11063-1, openSUSE-SU-2026:11064-1, openSUSE-SU-2026:11503-1, openSUSE-SU-2026:11507-1, openSUSE-SU-2026:11509-1, openSUSE-SU-2026:11840-1, openSUSE-SU-2026:21097-1 ## What is CVE-2026-11332? CVE-2026-11332 is a high-severity command injection vulnerability in Red Hat Migration Toolkit for Applications 8, published on 5 Jun 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link. ### Official 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. Weakness: CWE-88 (Improper Neutralization of Argument Delimiters in a Command) ## Which versions are affected by CVE-2026-11332? 11 open source packages ship an affected version, including ansible-core. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `ansible-core` | PyPI | All versions | 2.16.19rc1, 2.18.18rc1, 2.19.11rc1, 2.20.7rc1, 2.21.1rc1 | | `ansible-core` | PyPI | All versions | 2.16.19rc1 | | `ansible-core` | PyPI | All versions | 2.16.19rc1 | | `ansible-core` | PyPI | From 2.17.0b1 | 2.18.18rc1 | | `ansible-core` | PyPI | From 2.17.0b1 | 2.18.18rc1 | | `ansible-core` | PyPI | From 2.19.0b1 | 2.19.11rc1 | | `ansible-core` | PyPI | From 2.19.0b1 | 2.19.11rc1 | | `ansible-core` | PyPI | From 2.20.0b1 | 2.20.7rc1 | | `ansible-core` | PyPI | From 2.20.0b1 | 2.20.7rc1 | | `ansible-core` | PyPI | From 2.21.0b1 | 2.21.1rc1 | | `ansible-core` | PyPI | From 2.21.0b1 | 2.21.1rc1 | | `ansible-core` | AlmaLinux:10 | All versions | 1:2.16.16-2.el10_2.1 | | `ansible-test` | AlmaLinux:10 | All versions | 1:2.16.16-2.el10_2.1 | | `ansible-core` | AlmaLinux:8 | All versions | 2.16.3-4.el8_10 | | `ansible-test` | AlmaLinux:8 | All versions | 2.16.3-4.el8_10 | | `ansible-core` | AlmaLinux:9 | All versions | 1:2.14.18-3.el9_8.1 | | `ansible-test` | AlmaLinux:9 | All versions | 1:2.14.18-3.el9_8.1 | | `ansible-core` | Red Hat:enterprise_linux:10.2 | All versions | 1:2.16.16-2.el10_2.1 | | `ansible-test` | Red Hat:enterprise_linux:10.2 | All versions | 1:2.16.16-2.el10_2.1 | | `ansible-core` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.16.3-4.el8_10 | | `ansible-test` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.16.3-4.el8_10 | | `ansible-core` | Red Hat:enterprise_linux:9::appstream | All versions | 1:2.14.18-3.el9_8.1 | | `ansible-test` | Red Hat:enterprise_linux:9::appstream | All versions | 1:2.14.18-3.el9_8.1 | | `ansible-core` | Red Hat:enterprise_linux_eus:10.0 | All versions | 1:2.16.14-1.el10_0.1 | | `ansible-test` | Red Hat:enterprise_linux_eus:10.0 | All versions | 1:2.16.14-1.el10_0.1 | | `ansible-core` | Red Hat:rhel_e4s:9.4::appstream | All versions | 1:2.14.14-1.el9_4.1 | | `ansible-test` | Red Hat:rhel_e4s:9.4::appstream | All versions | 1:2.14.14-1.el9_4.1 | | `ansible-core` | Red Hat:rhel_eus:9.6::appstream | All versions | 1:2.14.18-1.el9_6.1 | | `ansible-test` | Red Hat:rhel_eus:9.6::appstream | All versions | 1:2.14.18-1.el9_6.1 | | `ansible-core` | Rocky Linux:10 | All versions | 1:2.16.16-2.el10_2.1 | | `ansible-core` | Rocky Linux:8 | All versions | 0:2.16.3-4.el8_10 | | `ansible-core` | Rocky Linux:9 | All versions | 1:2.14.18-3.el9_8.1 | | `ansible-core` | SUSE:Linux Enterprise Module for Package Hub 15 SP7 | All versions | 2.18.3-150400.9.14.1 | | `ansible-core` | SUSE:Linux Enterprise Module for Systems Management 15 SP7 | All versions | 2.18.3-150400.9.14.1 | | `ansible-core` | SUSE:Linux Enterprise Server 16.0 | All versions | 2.18.3-160000.3.1 | | `ansible-core` | SUSE:Linux Enterprise Server for SAP applications 16.0 | All versions | 2.18.3-160000.3.1 | | `ansible-core` | openSUSE:Leap 16.0 | All versions | 2.18.3-160000.3.1 | | `ansible-core` | openSUSE:Tumbleweed | All versions | 2.21.0-3.1 | | `ansible-core-2.18` | openSUSE:Tumbleweed | All versions | 2.18.18-1.1 | | `ansible-core-2.19` | openSUSE:Tumbleweed | All versions | 2.19.11-1.1 | ## How do I fix CVE-2026-11332? Upgrade ansible-core to a fixed version for your release line: 2.16.19rc1, 2.18.18rc1, 2.19.11rc1 or 2.20.7rc1. ## Is CVE-2026-11332 being exploited? There is no known exploitation of CVE-2026-11332 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-11332 and fix it if it is affected. What it is: CVE-2026-11332 is a high-severity command injection vulnerability in Red Hat Migration Toolkit for Applications 8, published on 5 Jun 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2026-11332 in the wild and no public exploit code. Affected packages and fixed versions: - ansible-core (PyPI): affected all versions; fixed in 2.16.19rc1, 2.18.18rc1, 2.19.11rc1, 2.20.7rc1, 2.21.1rc1 - ansible-core (PyPI): affected all versions; fixed in 2.16.19rc1 - ansible-core (PyPI): affected all versions; fixed in 2.16.19rc1 - ansible-core (PyPI): affected from 2.17.0b1; fixed in 2.18.18rc1 - ansible-core (PyPI): affected from 2.17.0b1; fixed in 2.18.18rc1 - ansible-core (PyPI): affected from 2.19.0b1; fixed in 2.19.11rc1 - ansible-core (PyPI): affected from 2.19.0b1; fixed in 2.19.11rc1 - ansible-core (PyPI): affected from 2.20.0b1; fixed in 2.20.7rc1 - ansible-core (PyPI): affected from 2.20.0b1; fixed in 2.20.7rc1 - ansible-core (PyPI): affected from 2.21.0b1; fixed in 2.21.1rc1 - ansible-core (PyPI): affected from 2.21.0b1; fixed in 2.21.1rc1 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-11332/ (Markdown: https://insights.sbomify.com/CVE-2026-11332/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-11332 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-11332 - OSV: https://osv.dev/vulnerability/CVE-2026-11332 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-11332/ Summaries are generated and may contain mistakes; the official description above is the record.