dbcve.org
TurborepoApplication · Vercel

CVE-2026-45772

CRITICAL · 9.8 CVSS v3.1 Published 2026-05-15
Fix available
A fix is available. Upgrade to 2.9.14 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Turborepo is a high-performance build system for JavaScript and TypeScript codebases. From 1.1.0 to before 2.9.14, 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. This vulnerability is fixed in 2.9.14.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Turborepo versions 1.1.0 through 2.9.13 execute yarn --version in the project directory to detect the package manager, which causes Yarn to load and execute a project-controlled yarnPath from .yarnrc.yml. An attacker who controls repository contents can inject malicious code via a crafted .yarnrc.yml that specifies a malicious yarnPath, leading to arbitrary code execution when users or CI systems run turbo, @turbo/codemod, or @turbo/workspace conversion commands.

MitigationUpgrade Turborepo to version 2.9.14 or later, which fixes the unsafe package manager detection. Additionally, audit repositories for any suspicious .yarnrc.yml files with unexpected yarnPath configurations.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
TurborepoApplication
Affected:>= 1.1.0, < 2.9.14

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Turborepo version
    Run `turbo --version` or inspect package.json dependencies for turbo, @turbo/codemod, or @turbo/workspace packages
    Affected if Version is >= 1.1.0 and < 2.9.14
  2. Locate .yarnrc.yml files in the repository
    Search for all .yarnrc.yml files in the project directory using `find . -name '.yarnrc.yml'` or similar
    Affected if A .yarnrc.yml file exists in the project or any subdirectory
  3. Inspect .yarnrc.yml for yarnPath configuration
    Open each .yarnrc.yml found and look for a `yarnPath:` directive
    Affected if The .yarnrc.yml contains a yarnPath setting that points to a file location
  4. Verify yarnPath source trustworthiness
    Examine the path specified in yarnPath - check if it points to a local file, remote URL, or an unexpected location within the repository
    Affected if The yarnPath points to a location controlled by an untrusted party or an unusual path within the repository

You are affected if Turborepo version is between 1.1.0 and 2.9.13 AND a .yarnrc.yml file with a yarnPath directive exists in the repository, as this combination allows arbitrary code execution via the package manager detection feature.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.9.14 or later
Fixed in 2.9.14
Interim mitigation

Upgrade Turborepo to version 2.9.14 or later, which fixes the unsafe package manager detection. Additionally, audit repositories for any suspicious .yarnrc.yml files with unexpected yarnPath configurations.

Recommended fix High confidence

2.9.14

  1. Upgrade Turborepo to version 2.9.14 or later by updating your package.json dependency or lockfile
  2. Verify the upgrade was successful by running `turbo --version` and confirming it shows 2.9.14 or higher

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Turborepo Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-45772 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-45772 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data