How severe is CVE-2026-45772?

No CVSS score has been assigned to CVE-2026-45772 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2026-45772?

CVE-2026-45772 affects the following packages: turbo (npm), @turbo/codemod (npm), @turbo/workspaces (npm). Ecosystems affected: npm.

How do I fix CVE-2026-45772?

Update turbo to 2.9.14 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-45772 is resolved across your whole dependency graph.

How do I detect CVE-2026-45772 in my npm dependencies?

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.

How do I mitigate CVE-2026-45772 if there is no patch (or I can't update yet)?

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.

Is CVE-2026-45772 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-45772 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-45772?

CVE-2026-45772 has an EPSS (Exploit Prediction Scoring System) score of 0.6%, placing it in the 49th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-45772?

CVE-2026-45772 is classified as CWE-426 (CWE-426). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2026-45772 published, and has it been updated?

CVE-2026-45772 was published on May 15, 2026 and was last updated on August 12, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

CVE-2026-45772 — turbo

CVE-2026-45772 is a CWE-426 vulnerability in turbo. A fix is available for turbo — see the affected versions and patch details below.

Turborepo: Unexpected local code execution during Yarn Berry detection

Also known asGHSA-3qcw-2rhx-2726

Published

May 15, 2026

Updated

Aug 12, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Exploitation data as of Sep 29, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

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 CVE-2026-45772.

EPSS Exploitation Probability

via FIRST.org ↗

0.6%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs49th percentile — riskier than 49% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

3 pkgs affected

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.

116other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

turbonpm

31.5Mdownloads / week

@turbo/codemodnpm

6Kdownloads / week

@turbo/workspacesnpm

566Kdownloads / week

Description

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

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`turbo`	≥ 1.1.0&&< 2.9.14	2.9.14`npm install turbo@2.9.14`
📦npm	`@turbo/codemod`	≥ 2.3.4&&< 2.9.14	2.9.14`npm install @turbo/codemod@2.9.14`
📦npm	`@turbo/workspaces`	≥ 2.3.4&&< 2.9.14	2.9.14`npm install @turbo/workspaces@2.9.14`

Affected Products

1 product · 1 configurations

Application

turborepovercel

≥ 1.1.0 && < 2.9.14

range

Detection & mitigation playbook

Open-source dependency

Detect
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 CVE-2026-45772 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

### 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 m

O3 Security · Impact-Aware SCA

Is CVE-2026-45772 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works