No analysis available yet.
Vendor Workaround
To mitigate this issue, configure the `ansible.python.activationScript` setting to "User" scope only within Visual Studio Code settings. This prevents untrusted project configurations from defining this setting in `.vscode/settings.json`. Users should always review the contents of `.vscode/settings.json` before opening or executing playbooks from untrusted sources. This action does not require a service restart or reload.
Tracking
Sign in to view the affected projects.
No advisories yet.
Wed, 22 Jul 2026 12:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | A flaw was found in the Ansible Lightspeed Visual Studio Code extension. This Command Injection vulnerability (CWE-78) allows a remote attacker to execute unauthorized commands on a user's system. The issue occurs because the `ansible.python.activationScript` setting, intended for a virtual environment activation script, does not properly validate user input as a file path. If a user opens or executes a specially crafted project, an attacker could exploit this to gain complete control over the user's system with the privileges of the Visual Studio Code application. | |
| Title | Ansible-lightspeed: ansible lightspeed visual studio code extension: arbitrary code execution via command injection in activation script setting | |
| First Time appeared |
Redhat
Redhat ansible Automation Platform |
|
| Weaknesses | CWE-78 | |
| CPEs | cpe:/a:redhat:ansible_automation_platform:2 | |
| Vendors & Products |
Redhat
Redhat ansible Automation Platform |
|
| References |
| |
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: redhat
Published:
Updated: 2026-07-22T12:06:42.591Z
Reserved: 2026-05-05T15:02:54.443Z
Link: CVE-2026-44190
No data.
No data.
No data.
OpenCVE Enrichment
No data.
-
CWE-78
Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')