← Back
CVE-2026-45773
medium
CVSS 6.5
Cross-Site Request Forgery (CSRF) in turbo (CVE-2026-45773)
Summary
vulnerability in turbo (CVE-2026-45773). Data can be tampered with by attackers. Exploitable via ``turbo``. Mitigation: upgrade to `2.9.14` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-45773** has been found in turbo.
Attackers can target a specific entry point like ``turbo`` over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 6.5/10.
What to do: upgrade turbo to **2.9.14** or later.
If unsure, ask your IT team or search "turbo CVE-2026-45773" on the vendor's site.
CVE-2026-45773 (turbo) — CWE-352 / CVSS v3 6.5
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: `turbo`
Patched: `2.9.14` — apply immediately
Workaround: 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.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**CSRF** (CWE-352) exists in turbo. Attackers reach the vulnerable code path via ``turbo`` without authentication.
📍 Affected scope
turbo — . Attack surface: `turbo`.
🔥 Severity
Severity: Medium (CVSS 6.5/10). Data can be tampered with by attackers
🔧 How to fix
Update to **2.9.14**.
🛡️ Workaround
Workaround: 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.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'turbo' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'turbo' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `turbo` を grep し、稼働しているサービス・バージョンを把握する。
-
5Apply temporary workaround mitigate
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.パッチが適用されるまでの応急処置として、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. を実施。回避策の副作用 (機能低下) を確認した上で。
-
6Apply patch patch
Upgrade turbo to 2.9.14ステージング環境で 2.9.14 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
npm
turbo
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.9.14"}]}]