GHSA-3qcw-2rhx-2726 — turbo
CRITICALGHSA-3qcw-2rhx-2726 is a critical-severity (CVSS 9.8) CWE-426 vulnerability in turbo. A fix is available for turbo — see the affected versions and patch details below.
Turbo: Unexpected local code execution during Yarn Berry detection
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-3qcw-2rhx-2726.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
GHSA-3qcw-2rhx-2726 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 380,526 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
turbonpm@turbo/codemodnpm@turbo/workspacesnpmDescription
Impact
Turborepo can be vulnerable to arbitrary code execution when run in untrusted repositories that contain malicious Yarn configuration. In affected versions, package manager detection executed yarn --version from the project directory, which could cause Yarn to load and execute a project-controlled yarnPath from .yarnrc.yml. An attacker who controls repository contents could cause code execution when a user or CI system runs affected turbo, @turbo/codemod, or @turbo/workspace conversion commands.
Fix
Turbo now avoids executing project-local Yarn during package manager detection. Yarn versions and paths are inferred from metadata such as package.json, parsing the value of yarnPath in .yarnrc.yml rather than executing it, and yarn.lock, and unrecognized Yarn lockfile formats are rejected instead of falling back to executing yarn.
Workarounds
If you cannot upgrade immediately, do not run Turborepo commands in untrusted repositories. Review or remove .yarnrc.yml files that define yarnPath before running Turborepo, especially in CI or automated tooling that processes external projects.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | turbo | ≥ 1.1.0&&< 2.9.14 | 2.9.14npm install turbo@2.9.14 |
| 📦npm | @turbo/codemod | ≥ 2.3.4&&< 2.9.14 | 2.9.14npm install @turbo/codemod@2.9.14 |
| 📦npm | @turbo/workspaces | ≥ 2.3.4&&< 2.9.14 | 2.9.14npm install @turbo/workspaces@2.9.14 |
Affected Products
turborepovercelDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for turbo, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update turbo to 2.9.14 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3qcw-2rhx-2726 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Frequently Asked Questions
Is GHSA-3qcw-2rhx-2726 in your dependencies?
Find it across npm, including transitive dependencies.