CVE-2026-34060
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedRuby 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceRuby LSP improperly interpolates the 'rubyLsp.branch' VS Code workspace setting into a generated Gemfile without sanitization, allowing arbitrary Ruby code injection via a malicious .vscode/settings.json file when a user opens the project.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 0.10.2< 0.26.9CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed Ruby LSP versionRun 'gem list ruby-lsp' to see the installed gem version, or check VS Code extensions for 'Shopify.ruby-lsp' versionAffected if Version is below 0.10.2 (gem) or below 0.26.9 (VS Code extension)
-
Locate VS Code settings fileLook for .vscode/settings.json in the project root directoryAffected if File exists and contains a 'rubyLsp.branch' setting
-
Inspect rubyLsp.branch setting valueOpen .vscode/settings.json and read the value of the 'rubyLsp.branch' keyAffected if The setting contains any Ruby syntax characters such as semicolons, backticks, system calls, or string interpolation syntax that could be interpreted as code
-
Verify Gemfile generation contextCheck if a Gemfile.lock exists and was recently modified, or look for Gemfile in the projectAffected if A Gemfile exists and the project was opened in VS Code with the Ruby LSP extension active
-
Check for injected code execution indicatorsReview the generated Gemfile for unexpected content after the branch name, particularly lines containing ';' or '`' charactersAffected if The Gemfile contains Ruby code or system commands beyond the intended branch name string
You are affected if you are running Ruby LSP versions below 0.10.2 or 0.26.9 and have a .vscode/settings.json file containing a 'rubyLsp.branch' setting that could inject arbitrary code when the project is opened.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped0.10.20.26.9
Update to ruby-lsp version 0.26.9 or later / Shopify.ruby-lsp version 0.10.2 or later to obtain the patched code that sanitizes the branch setting before Gemfile generation.
Shopify.ruby-lsp >= 0.10.2 OR ruby-lsp >= 0.26.9
- Upgrade the Shopify.ruby-lsp VS Code extension to version 0.10.2 or later
- Alternatively, upgrade the ruby-lsp gem to version 0.26.9 or later
- Verify the upgrade by checking the installed version matches or exceeds the fixed release
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-34060 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-34060 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data