← Back
CVE-2026-45036
high
CVSS 7.0
OS Command Injection in tabby (CVE-2026-45036)
Summary
OS command injection in tabby (CVE-2026-45036). Successful exploitation can lead to full system takeover. Mitigation: upgrade to `1.0.233` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-45036** has been found in tabby.
Successful exploitation can lead to full system takeover. CVSS score: 7.0/10.
What to do: upgrade tabby to **1.0.233** or later.
If unsure, ask your IT team or search "tabby CVE-2026-45036" on the vendor's site.
CVE-2026-45036 (tabby) — CWE-78 / CVSS v3 7.0
Attack vector: local / unauthenticated
Patched: `1.0.233` — apply immediately
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
**OS command injection** (CWE-78) exists in tabby.
📍 Affected scope
tabby — .
🔥 Severity
Severity: High (CVSS 7.0/10). Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **1.0.233**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'tabby' .` 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 'tabby' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `tabby` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade tabby to 1.0.233ステージング環境で 1.0.233 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
References
- patch [email protected]