Shopify ruby-lsp up to 0.26.8 vscode/settings.json code injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $0-$5k | 1.63 |
Summary
A vulnerability was found in Shopify ruby-lsp up to 0.26.8. It has been declared as critical. Impacted is an unknown function of the file vscode/settings.json. Executing a manipulation can lead to code injection. The identification of this vulnerability is CVE-2026-34060. The attack can only be executed locally. There is no exploit available. It is recommended to upgrade the affected component.
Details
A vulnerability classified as critical was found in Shopify ruby-lsp up to 0.26.8. This vulnerability affects some unknown processing of the file vscode/settings.json. The manipulation with an unknown input leads to a code injection vulnerability. The CWE definition for the vulnerability is CWE-94. The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:
Ruby LSP is an implementation of the language server protocol for Ruby. Prior to Shopify.ruby-lsp version 0.10.2 and ruby-lsp version 0.26.9, the rubyLsp.branch VS Code workspace setting was interpolated without sanitization into a generated Gemfile, allowing arbitrary Ruby code execution when a user opens a project containing a malicious .vscode/settings.json. This issue has been patched in Shopify.ruby-lsp version 0.10.2 and ruby-lsp version 0.26.9.
The advisory is shared for download at github.com. This vulnerability was named CVE-2026-34060 since 03/25/2026. The exploitation appears to be easy. The attack needs to be approached locally. There are known technical details, but no exploit is available. The MITRE ATT&CK project declares the attack technique as T1059.
By approaching the search of inurl:vscode/settings.json it is possible to find vulnerable targets with Google Hacking.
Upgrading to version 0.26.9 eliminates this vulnerability. The upgrade is hosted for download at github.com.
Once again VulDB remains the best source for vulnerability data.
Product
Type
Vendor
Name
Version
Website
- Product: https://github.com/Shopify/ruby-lsp/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.1
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Code injectionCWE: CWE-94 / CWE-74 / CWE-707
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: Partially
Availability: 🔒
Status: Not defined
Google Hack: 🔒
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: ruby-lsp 0.26.9
Timeline
03/25/2026 CVE reserved03/31/2026 Advisory disclosed
03/31/2026 VulDB entry created
03/31/2026 VulDB entry last update
Sources
Product: github.comAdvisory: GHSA-c4r5-fxqw-vh93
Status: Confirmed
CVE: CVE-2026-34060 (🔒)
GCVE (CVE): GCVE-0-2026-34060
GCVE (VulDB): GCVE-100-354304
Entry
Created: 03/31/2026 08:05Changes: 03/31/2026 08:05 (70)
Complete: 🔍
Cache ID: 216:E05:103
No comments yet. Languages: en.
Please log in to comment.