Command Injection in Turborepo (CVE-2026-46508)
Summary
Command injection in Turborepo (CVE-2026-46508). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 2.9.14000 or later.
Original description
The description as published by the source.
Turborepo is a high-performance build system for JavaScript and TypeScript codebases. Prior to 2.9.14000, the Turborepo LSP VS Code extension could execute shell commands derived from workspace-controlled values. The extension used string-based command execution for Turborepo daemon commands and task runs. A malicious workspace could provide crafted values through workspace settings or task names in the repository's source code that were interpolated into shell commands. When the extension activated or when a user ran a task through the extension, those values could be interpreted by the user's shell, allowing arbitrary command execution with the privileges of the local VS Code process. This vulnerability is fixed in 2.9.14000.
Source: NIST National Vulnerability Database NVD
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-46508 has been found in Turborepo.
Successful exploitation can lead to full system takeover. CVSS score: 7.8/10.
What to do: upgrade Turborepo to 2.9.14000 or later.
If unsure, ask your IT team or search "Turborepo CVE-2026-46508" on the vendor's site.
CVE-2026-46508 (Turborepo) — CWE-77 / CVSS v3 7.8
Attack vector: local / unauthenticated
Patched: 2.9.14000 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-77) exists in Turborepo.
Check the vendor advisory for the affected versions of Turborepo.
Severity: High (CVSS 7.8/10). Successful exploitation can lead to full system takeover.
Update to 2.9.14000.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'Turborepo' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'Turborepo' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Turborepoを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade Turborepo to 2.9.14000ステージング環境で 2.9.14000 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。