chore(deps): upgrade turbo to 2.9.14 to fix CSRF vulnerabilit#1731
Conversation
Signed-off-by: Arturo Reuschenbach Puncernau <reuschenbach@gmail.com>
|
There was a problem hiding this comment.
Pull request overview
This PR updates the monorepo’s build tooling dependencies to address a reported Turborepo CSRF vulnerability by upgrading turbo, and also bumps the pinned pnpm version used via packageManager.
Changes:
- Upgraded
turbofrom2.5.6to2.9.14. - Updated the root
packageManagerpin frompnpm@10.32.1topnpm@10.34.1. - Refreshed
pnpm-lock.yamlto reflect the new Turborepo package layout (@turbo/*optional binaries).
Reviewed changes
Copilot reviewed 1 out of 2 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| package.json | Bumps turbo and the pinned pnpm version via packageManager. |
| pnpm-lock.yaml | Updates the lockfile to match turbo@2.9.14 resolution and its platform-specific optional deps. |
Files not reviewed (1)
- pnpm-lock.yaml: Language not supported
Signed-off-by: Arturo Reuschenbach Puncernau <reuschenbach@gmail.com>
Summary
Upgrades
turbofrom 2.5.6 to 2.9.14 to fix a CSRF vulnerability in Turborepo's login callback flow (Dependabot alert #212).Security Impact: Turborepo's self-hosted login and SSO browser flows did not validate a CSRF state value on the localhost callback. A malicious web page could send a request to the local callback server with
an attacker-controlled token during authentication.
Changes Made
turbofrom 2.5.6 to 2.9.14 (security fix for CSRF vulnerability)pnpmfrom 10.32.1 to 10.34.1 (lockfile handling improvements)Related Issues
Screenshots (if applicable)
N/A - dependency upgrade only
Testing Instructions
pnpm ipnpm buildpnpm lintpnpm typecheckpnpm testChecklist
PR Manifesto
Review the PR Manifesto for best practises.