CVE-2026-44190 PUBLISHED

Ansible-lightspeed: ansible lightspeed visual studio code extension: arbitrary code execution via command injection in activation script setting

Assigner: redhat
Reserved: 05.05.2026 Published: 22.07.2026 Updated: 22.07.2026

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.

Metrics

CVSS Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
CVSS Score: 7.8

Product Status

Vendor Red Hat
Product Red Hat Ansible Automation Platform 2
Versions Default: affected
Vendor Red Hat
Product Red Hat Ansible Automation Platform 2
Versions Default: affected
Vendor Red Hat
Product Red Hat Ansible Automation Platform 2
Versions Default: affected

Workarounds

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.

Credits

  • This issue was discovered by Laura Pardo (Red Hat Inc.).

References

Problem Types

  • Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') CWE