Advisory

GHSA-3qcw-2rhx-2726

Also known as: CVE-2026-45772

Summary

Turbo: Unexpected local code execution during Yarn Berry detection

Details

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.

Severity

Low Basis: The source's own band: LOW

Dates

Published
2026-05-19 19:46 UTC
Modified
2026-09-10 03:51 UTC

Affected packages and fixes

turbo

npm · All systems

Affected

  • introduced 1.1.0, fixed 2.9.14 (semver)

Fixed versions

2.9.14

Fix

@turbo/codemod

npm · All systems

Affected

  • introduced 2.3.4, fixed 2.9.14 (semver)

Fixed versions

2.9.14

Fix

@turbo/workspaces

npm · All systems

Affected

  • introduced 2.3.4, fixed 2.9.14 (semver)

Fixed versions

2.9.14

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences