NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · npm

CVE-2026-45772: Turbo: Unexpected local code execution during Yarn Berry detection

lowCVSS 3.1 9.8GHSA-3qcw-2rhx-2726

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.

Published May 19, 2026

Affected packages

turbo

Ecosystem
npm
Affected
>= 1.1.0, < 2.9.14
Fixed in
2.9.14
Check
npm ls turbo

@turbo/codemod

Ecosystem
npm
Affected
>= 2.3.4, < 2.9.14
Fixed in
2.9.14
Check
npm ls @turbo/codemod

@turbo/workspaces

Ecosystem
npm
Affected
>= 2.3.4, < 2.9.14
Fixed in
2.9.14
Check
npm ls @turbo/workspaces

Advisory details

From the GitHub Advisory Database (CC BY 4.0).

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.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology

More npm vulnerabilities

All npm entries