CVE-2026-45773: vercel turborepo · Cross-Site Request Forgery (CSRF)
Affects vercel turborepoSource CVE Database V5
Not known to be exploited · CVSS 5.1 Medium : upgrade to 2.9.14 when convenient.
Data as of 30 Oct 2026, 06:59 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 2% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.9.14
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:N/VI:L/VA:N/SC:L/SI:H/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 15 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
Upgrade vercel turborepo to 2.9.14.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| vercelturborepo | Affected
| Fixed in
|
AI-suggested
This vulnerability is fixed in turborepo version 2.9.14. Users should upgrade to version 2.9.14 or later to remediate this issue. Since the product is self-hosted, the vendor does not manage remediation automatically. Patch status is confirmed by the vendor advisory indicating the fix in 2.9.14. No additional mitigations are specified.
Description
A Cross-Site Request Forgery (CSRF) vulnerability exists in vercel turborepo versions prior to 2.9.14. The issue occurs in the self-hosted login and SSO browser flows where the CSRF state value on the localhost callback was not validated. This allows a malicious web page to send a request with an attacker-controlled token to the local callback server, potentially causing the CLI to complete login with incorrect credentials. Vercel-hosted login flows using device authorization are not affected. The vulnerability is fixed in version 2.9.14.