Categories
CVE-2026-45772 critical CVSS 9.8

Vulnerability in turbo (CVE-2026-45772)

Summary

Vulnerability in turbo (CVE-2026-45772). Successful exploitation can lead to full system takeover. Exploitable via yarnPath. Mitigation: upgrade to 2.9.14 or later.

Original description

The description as published by the source.

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.

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-45772 has been found in turbo.
Attackers can target a specific entry point like yarnPath over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 9.8/10.
What to do: upgrade turbo to 2.9.14 or later.
If unsure, ask your IT team or search "turbo CVE-2026-45772" on the vendor's site.

CVE-2026-45772 (turbo) — CWE-426 / CVSS v3 9.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: yarnPath / turbo / yarn.lock / yarn
Patched: 2.9.14 — apply immediately
Workaround: If you cannot upgrade immediately, do not run Turborepo commands in untrusted repositories.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-426) exists in turbo. Attackers reach the vulnerable code path via yarnPath without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of turbo. Attack surface: yarnPath / turbo / yarn.lock / yarn.

🔥 Severity

Severity: Critical (CVSS 9.8/10). Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 2.9.14.

🛡️ Workaround

Workaround: If you cannot upgrade immediately, do not run Turborepo commands in untrusted repositories.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'turbo' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    grep -r 'turbo' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で turbo を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply temporary workaround mitigate
    If you cannot upgrade immediately, do not run Turborepo commands in untrusted repositories.

    パッチが適用されるまでの応急処置として、If you cannot upgrade immediately, do not run Turborepo commands in untrusted repositories. を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 3
    Apply patch patch
    Upgrade turbo to 2.9.14

    ステージング環境で 2.9.14 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  4. 4
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

npm turbo
[{"type":"SEMVER","events":[{"introduced":"1.1.0"},{"fixed":"2.9.14"}]}]
npm @turbo/codemod
[{"type":"SEMVER","events":[{"introduced":"2.3.4"},{"fixed":"2.9.14"}]}]
npm @turbo/workspaces
[{"type":"SEMVER","events":[{"introduced":"2.3.4"},{"fixed":"2.9.14"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details