EUVD-2026-47655
GHSA-63fx-4hcp-68gg
Severity by source
AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Attacker needs no account (payload delivered via workspace, PR:N) but victim must open the malicious project locally (AV:L, UI:R); full C/I/A as arbitrary code runs with the user's privileges (S:U).
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 the Visual Studio Code Ansible Lightspeed extension. This command injection vulnerability (CWE-78) arises from improper handling of the ansible.executionEnvironment.containerOptions and ansible.executionEnvironment.volumeMounts settings, allowing an attacker to inject shell separators. This can be triggered automatically during Language Server initialization or manually when executing a playbook. Successful exploitation leads to remote code execution (RCE) on the victim's machine with the privileges of the Visual Studio Code user, potentially resulting in a complete system compromise.
AnalysisAI
Local code execution in the Visual Studio Code Ansible (Lightspeed) extension lets a malicious project run arbitrary shell commands on a developer's machine by abusing the ansible.executionEnvironment.containerOptions and volumeMounts settings, which fail to sanitize shell separators (CWE-78). Because these are workspace-scoped settings, simply opening a booby-trapped repository can auto-trigger execution during Language Server initialization, yielding code execution as the VS Code user. …
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 the victim to open, in VS Code with the Ansible/Lightspeed extension installed, a workspace where the attacker controls the ansible.executionEnvironment.containerOptions or ansible.executionEnvironment.volumeMounts settings (typically via a repository-supplied .vscode/settings.json) and where the execution-environment feature is in use; the injected shell separators are then processed automatically when the Language Server initializes or manually when a playbook is executed. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | Signals are largely consistent and point to a genuine but interaction-gated developer-workstation risk rather than a mass-exploitable server flaw. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker publishes an innocuous-looking Ansible role or playbook repository whose .vscode/settings.json sets ansible.executionEnvironment.containerOptions to a value containing shell separators and an appended payload (e.g., a reverse shell). A developer clones and opens the repo in VS Code; during Ansible Language Server initialization the crafted option is concatenated into a container command and the injected commands execute as that user. … |
| Remediation | Update the Visual Studio Code Ansible/Ansible Lightspeed extension to the fixed release once available and monitor the Red Hat advisory at https://access.redhat.com/security/cve/CVE-2026-44191 and Bugzilla https://bugzilla.redhat.com/show_bug.cgi?id=2466761 for the exact patched version, which is not stated in the available data (no vendor-released fix version independently confirmed). … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours: identify all staff using the Ansible Lightspeed extension and advise them to avoid opening untrusted repositories; audit recent repository clones for suspicious external sources. …
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
Arbitrary command execution in ansible-core allows an attacker who controls a collection source URI to run commands on a
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
Same weakness CWE-78 – OS Command Injection
View allVendor StatusVendor
Share
External POC / Exploit Code
Leaving vuln.today