High [CVE-2026-11332 +1] argument injection in ansible-galaxy collection install via git clone (incomplete fix for CVE-2026-11332)
This high-severity Red Hat Linux advisory covers CVE-2026-16493 and CVE-2026-11332 affecting Red Hat Satellite 6.17 for RHEL 9, Red Hat Satellite 6.18 for RHEL 9, Red Hat Satellite 6.19 for RHEL 9.
Aggregated and source-linked by VulniPulse. Data sources, validation and limitations. This bulletin covers 2 CVEs; its score, affected versions and guidance may apply to different issues within that bulletin.
VulniPulse record published Record updated
Android app · Google Play
Monitor future Red Hat Linux CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.
Summary
A flaw was found in ansible-core. An attacker who provides a crafted collection source URI containing git argument injection payloads can achieve arbitrary command execution when a user runs 'ansible-galaxy collection install' with the malicious source.
This is an incomplete fix for CVE-2026-11332, which hardened the role install path but missed the equivalent collection install code path. Red Hat has assessed this vulnerability as Important because it allows arbitrary command execution when a user installs a collection from a crafted git source.
Users who install collections exclusively from Ansible Galaxy or Automation Hub (HTTPS sources) are not exposed to this specific flaw. Red Hat severity: Important — CVSS 7.8 (CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H).
Weakness: CWE-88. Affected Red Hat products: Red Hat Satellite 6.17 for RHEL 9; Red Hat Satellite 6.18 for RHEL 9; Red Hat Satellite 6.19 for RHEL 9; Red Hat Ansible Automation Platform 2; Red Hat Enterprise Linux 10; Red Hat Enterprise Linux 8; Red Hat Enterprise Linux 9.
Red Hat fixing advisory: RHSA-2026:63387, RHSA-2026:63386, RHSA-2026:63385.
Affected products named by the advisory: Red Hat package: ansible-core.
Affected versions
No affected-version range was extracted from the source record. The vendor advisory is authoritative — check it before change work.
Official advisory · high-confidence parse· fetched 23 days ago·verify at source
- ansible-core-1:2.16.19-1.el9sat
- pulpcore-obsolete-packages-0:1.3.1-5.el9pc
- python3.12-pulpcore-0:3.73.30-3.el9pc
- RHSA-2026:63387
- RHSA-2026:63386
- RHSA-2026:63385
Official advisory · high-confidence parse· fetched 23 days ago·verify at source
Mitigation checklist
- The following practices would help for avoiding exposure and mitigate this flaw: 1. Do not install Ansible collections from untrusted or unverified git sources. Only install collections from trusted sources such as Ansible Galaxy (https://galaxy.ansible.com), Red Hat Automation Hub (https://console.redhat.com/ansible/automation-hub), or verified internal repositories using HTTPS URLs. 2. Carefully inspect any requirements.yml files before running 'ansible-galaxy collection install -r requirements.yml'. Verify that all collection sources use legitimate HTTPS URLs and do not contain git+ prefixed URIs with suspicious characters (especially values starting with '-'). 3. Ensure your system's git version is 2.12 or later, which disables the ext:: transport by default. While this does not fully prevent exploitation (the -ccore.sshCommand technique bypasses transport restrictions), it eliminates one of the exploitation vectors. 4. Restrict the GIT_ALLOW_PROTOCOL environment variable to only necessary protocols (e.g. https, ssh) and never include 'ext' unless absolutely required.
Official advisory · high-confidence parse· fetched 23 days ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.