Skip to content

Workspace settings can override executable and Gemfile paths used by the Ruby LSP VS Code extension

Moderate
alexcrocha published GHSA-2x7g-8mp4-572w May 21, 2026

Package

Shopify.ruby-lsp (VS Code Extension)

Affected versions

<= 0.10.3

Patched versions

0.10.4

Description

Summary

Several workspace-level settings in the Ruby LSP VS Code extension could override the path to the Ruby executable, the version manager executables, or the Bundler Gemfile used at startup. A malicious repository containing a .vscode/settings.json could set these values to attacker-controlled targets. Opening and trusting the repository would then execute code with the privileges of the developer.

The Ruby LSP gem and clients of the language server in other editors are not affected.

Details

The settings rubyLsp.rubyExecutablePath, rubyLsp.bundleGemfile, and the path settings under rubyLsp.rubyVersionManager (the asdf, mise, rbenv, rv executable paths and chrubyRubies) did not declare "scope": "machine" in vscode/package.json. As a result, they could be set from a workspace .vscode/settings.json file.

When activation ran with a workspace-supplied value for rubyExecutablePath, the value was interpolated into a shell command and executed through Node's shell-invoking subprocess call. Shell metacharacters in the value were interpreted by the user's shell, allowing arbitrary command execution. The related version-manager path settings followed the same pattern and could lead to the same outcome through their respective managers. Similarly, bundleGemfile controlled which Gemfile Bundler evaluated at startup, which could also result in code execution through Bundler.

Impact

Code execution with the privileges of the user who opens and trusts the malicious project. Exploitation requires the developer to open a workspace containing an attacker-supplied .vscode/settings.json and accept the VS Code Workspace Trust prompt. Once the user has trusted the workspace, the affected settings could redirect the Ruby executable, the version manager executables, or the Bundler Gemfile to attacker-controlled targets.

This vulnerability is in the VS Code extension only. The ruby-lsp gem is not affected.

Remediation

VS Code extension version 0.10.4 and later restrict the affected settings to user and machine scope only. Workspace .vscode/settings.json files can no longer set them. The extension also declares a capabilities.untrustedWorkspaces block listing rubyLsp.rubyExecutablePath, rubyLsp.customRubyCommand, rubyLsp.rubyVersionManager, and rubyLsp.bundleGemfile in restrictedConfigurations, ensuring these settings are ignored in untrusted workspaces.

VS Code extensions auto-update by default, so most users will receive the fix without action. Users who have disabled auto-updates should update to extension version >= 0.10.4.

Action required if you previously set any of these in workspace settings: the values will now be silently ignored when set at the workspace level. Move them to user or machine settings to retain the configuration.

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v4 base metrics

Exploitability Metrics
Attack Vector Local
Attack Complexity Low
Attack Requirements Present
Privileges Required Low
User interaction Active
Vulnerable System Impact Metrics
Confidentiality High
Integrity High
Availability High
Subsequent System Impact Metrics
Confidentiality None
Integrity None
Availability None

CVSS v4 base metrics

Exploitability Metrics
Attack Vector: This metric reflects the context by which vulnerability exploitation is possible. This metric value (and consequently the resulting severity) will be larger the more remote (logically, and physically) an attacker can be in order to exploit the vulnerable system. The assumption is that the number of potential attackers for a vulnerability that could be exploited from across a network is larger than the number of potential attackers that could exploit a vulnerability requiring physical access to a device, and therefore warrants a greater severity.
Attack Complexity: This metric captures measurable actions that must be taken by the attacker to actively evade or circumvent existing built-in security-enhancing conditions in order to obtain a working exploit. These are conditions whose primary purpose is to increase security and/or increase exploit engineering complexity. A vulnerability exploitable without a target-specific variable has a lower complexity than a vulnerability that would require non-trivial customization. This metric is meant to capture security mechanisms utilized by the vulnerable system.
Attack Requirements: This metric captures the prerequisite deployment and execution conditions or variables of the vulnerable system that enable the attack. These differ from security-enhancing techniques/technologies (ref Attack Complexity) as the primary purpose of these conditions is not to explicitly mitigate attacks, but rather, emerge naturally as a consequence of the deployment and execution of the vulnerable system.
Privileges Required: This metric describes the level of privileges an attacker must possess prior to successfully exploiting the vulnerability. The method by which the attacker obtains privileged credentials prior to the attack (e.g., free trial accounts), is outside the scope of this metric. Generally, self-service provisioned accounts do not constitute a privilege requirement if the attacker can grant themselves privileges as part of the attack.
User interaction: This metric captures the requirement for a human user, other than the attacker, to participate in the successful compromise of the vulnerable system. This metric determines whether the vulnerability can be exploited solely at the will of the attacker, or whether a separate user (or user-initiated process) must participate in some manner.
Vulnerable System Impact Metrics
Confidentiality: This metric measures the impact to the confidentiality of the information managed by the VULNERABLE SYSTEM due to a successfully exploited vulnerability. Confidentiality refers to limiting information access and disclosure to only authorized users, as well as preventing access by, or disclosure to, unauthorized ones.
Integrity: This metric measures the impact to integrity of a successfully exploited vulnerability. Integrity refers to the trustworthiness and veracity of information. Integrity of the VULNERABLE SYSTEM is impacted when an attacker makes unauthorized modification of system data. Integrity is also impacted when a system user can repudiate critical actions taken in the context of the system (e.g. due to insufficient logging).
Availability: This metric measures the impact to the availability of the VULNERABLE SYSTEM resulting from a successfully exploited vulnerability. While the Confidentiality and Integrity impact metrics apply to the loss of confidentiality or integrity of data (e.g., information, files) used by the system, this metric refers to the loss of availability of the impacted system itself, such as a networked service (e.g., web, database, email). Since availability refers to the accessibility of information resources, attacks that consume network bandwidth, processor cycles, or disk space all impact the availability of a system.
Subsequent System Impact Metrics
Confidentiality: This metric measures the impact to the confidentiality of the information managed by the SUBSEQUENT SYSTEM due to a successfully exploited vulnerability. Confidentiality refers to limiting information access and disclosure to only authorized users, as well as preventing access by, or disclosure to, unauthorized ones.
Integrity: This metric measures the impact to integrity of a successfully exploited vulnerability. Integrity refers to the trustworthiness and veracity of information. Integrity of the SUBSEQUENT SYSTEM is impacted when an attacker makes unauthorized modification of system data. Integrity is also impacted when a system user can repudiate critical actions taken in the context of the system (e.g. due to insufficient logging).
Availability: This metric measures the impact to the availability of the SUBSEQUENT SYSTEM resulting from a successfully exploited vulnerability. While the Confidentiality and Integrity impact metrics apply to the loss of confidentiality or integrity of data (e.g., information, files) used by the system, this metric refers to the loss of availability of the impacted system itself, such as a networked service (e.g., web, database, email). Since availability refers to the accessibility of information resources, attacks that consume network bandwidth, processor cycles, or disk space all impact the availability of a system.
CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

CVE ID

CVE-2026-48122

Weaknesses

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

The product constructs all or part of an OS command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended OS command when it is sent to a downstream component. Learn more on MITRE.

Credits