EUVD-2026-46336
GHSA-m37p-hmh2-w6j2
Severity by source
AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Attacker needs no privileges (PR:N) but the victim must locally run the install command (AV:L/UI:R); injected command runs as that user with full C/I/A impact and no scope change.
Primary rating from Vendor (redhat).
CVSS VectorVendor: redhat
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Lifecycle Timeline
2DescriptionCVE.org
A flaw was found in ansible-core. The _extract_collection_from_git() function in ansible-core's concrete_artifact_manager.py constructs git clone commands without a '--' (end-of-options) separator before user-supplied URLs when installing collections from git sources. 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.
AnalysisAI
Arbitrary command execution in ansible-core allows an attacker who controls a collection source URI to run commands on a victim's machine when that victim executes 'ansible-galaxy collection install' against the malicious git source. The flaw lives in _extract_collection_from_git() in concrete_artifact_manager.py, which builds git clone commands without a '--' end-of-options separator, letting crafted URIs be parsed as git arguments. …
Unlock full vulnerability intelligence
- Risk assessment & exploitation conditions
- Attack chain visualization
- Remediation with exact patch versions
- Threat intelligence from 22 sources
- Personal watchlist & email alerts
Free forever · No credit card required
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata
Vulnerability AssessmentAI
| Exploitation | Exploitation requires that a victim actively run 'ansible-galaxy collection install' with an attacker-supplied git source URI (per AV:L/UI:R) - the vulnerable path is specifically the git-based collection install in _extract_collection_from_git(), so installs from Automation Hub, tarballs, or non-git sources are not affected. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The CVSS 3.1 vector CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H yields 7.8 (High), and the metrics are internally consistent with the description: exploitation is local and requires no attacker privileges (PR:N) but does require the victim to actively run an install command (UI:R), producing full confidentiality, integrity, and availability impact in the victim's security context. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker publishes or advertises a collection whose git source URI is crafted to begin with a git option payload (for example abusing option-style arguments or the ext:: transport) and persuades a developer or automation operator to install it. When the victim runs 'ansible-galaxy collection install' pointing at that source, git interprets the crafted URI as an argument and the attacker's command executes with the victim's privileges. … |
| Remediation | No vendor-released patch version was identified in the provided data, so the primary action is to monitor and apply the Red Hat erratum referenced at https://access.redhat.com/security/cve/CVE-2026-16493 and track https://bugzilla.redhat.com/show_bug.cgi?id=2503724 for the fixed ansible-core package versions across RHEL 8/9/10, Ansible Automation Platform 2, and Satellite 6, then upgrade to those releases once published. … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours: inventory all systems and playbooks executing ansible-galaxy collection install against external or untrusted repository sources; audit collection manifests to identify any external dependencies installed in the past 90 days; establish immediate restriction on new external collection installations pending mitigation. …
Sign in for detailed remediation steps and compensating controls.
Threat intelligence, references, and detailed analysis are available after sign-in.
Credential disclosure in Red Hat Ansible Automation Platform 2.5 and 2.6 allows any authenticated user to retrieve plain
Arbitrary file write in pulpcore's FilesystemExport feature allows an authenticated administrator to escape the intended
mTLS authentication bypass in the Red Hat Ansible Automation Platform (AAP) Gateway Envoy proxy allows unauthenticated r
Local code execution in the Visual Studio Code Ansible (Lightspeed) extension lets a malicious project run arbitrary she
Remote code execution in galaxy_ng's legacy role import API (v1) allows an authenticated user controlling a git reposito
Incomplete RBAC authorization in AWX's websocket event consumer exposes real-time job stdout to any authenticated user,
Container privilege escalation in Red Hat Ansible Automation Platform 2 allows non-root users within affected container
Server-Side Request Forgery in AWX's GitHub webhook integration (Red Hat Ansible Automation Platform 2) enables a remote
Insufficient OAuth token invalidation in Ansible Lightspeed (part of Red Hat Ansible Automation Platform 2.x) allows a r
Path traversal in awxkit's YAML !include directive exposes arbitrary local files when a user imports a crafted YAML file
Vendor StatusVendor
Share
External POC / Exploit Code
Leaving vuln.today