CVE-2026-45773: Turborepo: Login callback CSRF/session fixation
Impact
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.
Fix
The login and SSO redirect flows now generate a random state value, include it in the browser authentication URL, and require the same value on the localhost callback before accepting a token. Callbacks with a missing or mismatched state are rejected.
Workarounds
If you cannot upgrade immediately, avoid browser-based self-hosted turbo login or SSO flows on machines that may load untrusted web content during authentication. Use a pre-provisioned token or environment-based authentication instead.
Other sources
Turborepo 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.
— MITRE
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-45773?
CVE-2026-45773 is considered a high severity vulnerability due to potential session fixation and CSRF exploits.
How do I fix CVE-2026-45773?
To fix CVE-2026-45773, upgrade Vercel Turborepo to version 2.9.14 or later.
What types of attacks can exploit CVE-2026-45773?
CVE-2026-45773 can be exploited through CSRF attacks and session fixation vulnerabilities.
Which versions of Vercel Turborepo are affected by CVE-2026-45773?
Versions of Vercel Turborepo prior to 2.9.14 are affected by CVE-2026-45773.
Is there a workaround for CVE-2026-45773 until I can update?
There is no official workaround for CVE-2026-45773; upgrading to the latest version is recommended.