CVE-2026-45773
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 · uneditedTurborepo is a high-performance build system for JavaScript and TypeScript codebases. Prior to 2.9.14, Turborepo's self-hosted login and SSO browser flows did not validate a CSRF state value on the localhost callback. While the CLI was waiting for authentication, a malicious web page could send a request to the local callback server with an attacker-controlled token. If accepted before the legitimate callback, the CLI could complete login with the wrong credentials. This affects users authenticating the turbo CLI against self-hosted remote cache/auth endpoints. Vercel-hosted login flows using device authorization are not affected. 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 confidenceTurborepo's self-hosted login and SSO browser flows fail to validate a CSRF state value on the localhost callback. An attacker can exploit this by sending a malicious request with an attacker-controlled token to the local callback server while the CLI waits for legitimate authentication. If the attacker's request is accepted first, the CLI completes login with the attacker's credentials instead of the user's.
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< 2.9.14CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Check Turborepo installation and versionRun `turbo --version` in your terminal or inspect your package.json / package-lock.json / pnpm-lock.yaml / yarn.lock for the turbo dependency versionAffected if The installed version is below 2.9.14 (e.g., 2.9.13, 2.9.0, 2.0.0, 1.x.x, etc.)
-
Identify if self-hosted remote cache or auth is configuredCheck your Turborepo configuration files (typically turbo.json) and environment variables for `TURBO_REMOTE_CACHE`, `TURBO_API`, or custom remote cache host settings. Also check if `.turbo` config directory contains self-hosted auth server settingsAffected if Self-hosted remote cache or custom authentication endpoints are configured and in use
-
Determine if login/SSO flows are in useInspect your CI/CD pipelines, scripts, or documentation for `turbo login`, `turbo logout`, or SSO configuration commands. Check for presence of `--api`, `--token`, or custom auth-related flags in turbo commandsAffected if Self-hosted login or SSO browser authentication flows are executed, as this vulnerability specifically targets the localhost callback during those flows
You are affected if you are running Turborepo versions below 2.9.14 AND using self-hosted login or SSO authentication flows with a local callback server.
Generated from the published advisory. Verify against your own configuration.
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 · scoped2.9.14
Upgrade Turborepo to version 2.9.14 or later to obtain the CSRF state validation fix. Self-hosted remote cache/auth deployments should prioritize this update.
2.9.14
- Upgrade Turborepo to version 2.9.14 or later by updating your dependency (e.g., npm install turbo@^2.9.14, yarn add turbo@^2.9.14, or pnpm add turbo@^2.9.14)
- Verify the installed turbo version is 2.9.14 or higher using `turbo --version`
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,192.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-45773 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-45773 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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