CVE-2026-45772

Turbo: Unexpected local code execution during Yarn Berry detection

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.

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.

CVE-2026-45772 has a CVSS score of 9.8 (Low). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.9.14); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

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.

1. What is CVE-2026-45772? CVE-2026-45772 is a low-severity security vulnerability in turbo (npm), affecting versions >= 1.1.0, < 2.9.14. It is fixed in 2.9.14.
2. How severe is CVE-2026-45772? CVE-2026-45772 has a CVSS score of 9.8 (Low). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which packages are affected by CVE-2026-45772?
   • turbo (npm) (versions >= 1.1.0, < 2.9.14)
   • @turbo/codemod (npm) (versions >= 2.3.4, < 2.9.14)
   • @turbo/workspaces (npm) (versions >= 2.3.4, < 2.9.14)
4. Is there a fix for CVE-2026-45772? Yes. CVE-2026-45772 is fixed in 2.9.14. Upgrade to this version or later.
5. Is CVE-2026-45772 exploitable, and should I be worried? Whether CVE-2026-45772 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-45772 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-45772?
   • Upgrade turbo to 2.9.14 or later
   • Upgrade @turbo/codemod to 2.9.14 or later
   • Upgrade @turbo/workspaces to 2.9.14 or later

Other vulnerabilities in turbo