CVE-2026-44191: VS Code Ansible Lightspeed RCE Flaw

CVE-2026-44191 Overview

CVE-2026-44191 is a command injection vulnerability in the Visual Studio Code Ansible Lightspeed extension. The flaw resides in the handling of the ansible.executionEnvironment.containerOptions and ansible.executionEnvironment.volumeMounts settings. Attackers can inject shell separators into these configuration values, allowing arbitrary commands to execute. Exploitation triggers automatically during Language Server initialization or manually when a user runs a playbook. Successful exploitation results in remote code execution on the victim's machine with the privileges of the Visual Studio Code user. The issue is tracked under [CWE-78] (Improper Neutralization of Special Elements used in an OS Command).

Critical Impact
Attackers can achieve remote code execution on the victim host with the privileges of the VS Code user, potentially leading to complete system compromise.

Affected Products

Visual Studio Code Ansible Lightspeed extension
Environments using ansible.executionEnvironment.containerOptions configuration
Environments using ansible.executionEnvironment.volumeMounts configuration

Discovery Timeline

2026-07-22 - CVE CVE-2026-44191 published to NVD
2026-07-22 - Last updated in NVD database

Technical Details for CVE-2026-44191

Vulnerability Analysis

The Ansible Lightspeed extension for Visual Studio Code exposes two configuration settings that control how execution environments are launched: ansible.executionEnvironment.containerOptions and ansible.executionEnvironment.volumeMounts. The extension passes these values into shell commands without properly neutralizing shell metacharacters. An attacker who controls or influences these settings can embed shell separators such as ;, &&, or backticks to break out of the intended command context. The injected commands run in the context of the Visual Studio Code process, granting the attacker the same privileges as the developer using the IDE.

Root Cause

The root cause is improper neutralization of special elements used in an OS command, classified as [CWE-78]. The extension constructs command lines by concatenating user-controlled configuration values into shell invocations. Because the values are not sanitized or passed through an argv-style API that avoids shell interpretation, embedded separators are interpreted by the shell as command boundaries.

Attack Vector

Two trigger paths lead to exploitation. First, the payload executes automatically when the Ansible Language Server initializes, meaning simply opening a workspace with a malicious .vscode/settings.json can achieve code execution. Second, execution occurs when a user manually runs a playbook that references the tainted execution environment settings. The vector requires local access and user interaction, such as opening an attacker-supplied repository or workspace. See the Red Hat CVE-2026-44191 Advisory for additional context.

Detection Methods for CVE-2026-44191

Indicators of Compromise

Unexpected child processes spawned by the Visual Studio Code process (code, Code.exe) or by the Ansible Language Server executable shortly after workspace load.
Presence of shell metacharacters such as ;, &&, |, or backticks inside ansible.executionEnvironment.containerOptions or ansible.executionEnvironment.volumeMounts values in .vscode/settings.json or user settings.
Outbound network connections initiated by sh, bash, cmd.exe, or powershell.exe originating from the VS Code process tree.

Detection Strategies

Inspect workspace and user-level VS Code settings for suspicious characters in Ansible execution environment fields before opening untrusted repositories.
Monitor process creation telemetry for shell interpreters launched as descendants of the VS Code or Ansible Language Server processes.
Correlate file writes to .vscode/settings.json with subsequent execution of unusual binaries during Language Server startup.

Monitoring Recommendations

Enable endpoint process tree logging on developer workstations and alert on shell spawns from IDE processes.
Flag Git clone or checkout operations followed immediately by execution of unfamiliar processes under the user's context.
Review Ansible Lightspeed extension logs for command lines containing injected separators or unexpected arguments.

How to Mitigate CVE-2026-44191

Immediate Actions Required

Update the Ansible Lightspeed extension to the latest patched release published by Red Hat. Refer to the Red Hat CVE-2026-44191 Advisory for fixed versions.
Audit all workspace .vscode/settings.json files for unsanitized values in ansible.executionEnvironment.containerOptions and ansible.executionEnvironment.volumeMounts.
Disable Workspace Trust auto-approval and require explicit trust before opening repositories from untrusted sources.

Patch Information

Red Hat has published tracking information for this vulnerability in Red Hat Bug Report #2466761 and the Red Hat CVE-2026-44191 Advisory. Apply the vendor-supplied update to the Ansible Lightspeed extension. Confirm the installed version through the VS Code Extensions view after the update.

Workarounds

Disable or uninstall the Ansible Lightspeed extension until a patched version is deployed.
Set the execution environment to disabled by configuring ansible.executionEnvironment.enabled to false in trusted user settings.
Open untrusted repositories in VS Code Restricted Mode to prevent automatic Language Server initialization with workspace-supplied settings.

bash

# Example: disable Ansible execution environment in user settings.json
{
  "ansible.executionEnvironment.enabled": false,
  "security.workspace.trust.untrustedFiles": "prompt",
  "security.workspace.trust.enabled": true
}