CVE-2026-45773: CWE-352: Cross-Site Request Forgery (CSRF) in vercel turborepo
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.
AI Analysis
Technical Summary
CVE-2026-45773 describes a CSRF vulnerability in vercel turborepo's self-hosted login and SSO browser flows prior to version 2.9.14. The localhost callback did not validate the CSRF state value, enabling an attacker to send a malicious request with an attacker-controlled token while the CLI awaited authentication. If this malicious request is accepted before the legitimate callback, the CLI could authenticate with 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 impacted. The issue is resolved in turborepo version 2.9.14.
Potential Impact
An attacker controlling a malicious web page can exploit this vulnerability to cause the turborepo CLI to complete login with attacker-supplied credentials instead of the legitimate user's credentials when using self-hosted remote cache/auth endpoints. This could lead to unauthorized access or actions performed under the attacker's identity. The vulnerability does not affect Vercel-hosted login flows using device authorization.
Mitigation Recommendations
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.
CVE-2026-45773: CWE-352: Cross-Site Request Forgery (CSRF) in vercel turborepo
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.
CVSS v4.0
Score 5.1medium
Affected software
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-45773 describes a CSRF vulnerability in vercel turborepo's self-hosted login and SSO browser flows prior to version 2.9.14. The localhost callback did not validate the CSRF state value, enabling an attacker to send a malicious request with an attacker-controlled token while the CLI awaited authentication. If this malicious request is accepted before the legitimate callback, the CLI could authenticate with 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 impacted. The issue is resolved in turborepo version 2.9.14.
Potential Impact
An attacker controlling a malicious web page can exploit this vulnerability to cause the turborepo CLI to complete login with attacker-supplied credentials instead of the legitimate user's credentials when using self-hosted remote cache/auth endpoints. This could lead to unauthorized access or actions performed under the attacker's identity. The vulnerability does not affect Vercel-hosted login flows using device authorization.
Mitigation Recommendations
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.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-05-13T07:45:21.251Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a074490ec166c07b0660928
Added to database: 05/15/2026, 16:06:40 UTC
Last enriched: 06/29/2026, 22:29:59 UTC
Last updated: 07/31/2026, 19:22:59 UTC
Views: 100
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.