OS Command Injection in Tabby (CVE-2026-45035)
Summary
OS command injection in Tabby (CVE-2026-45035). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 1.0.233 or later.
Original description
The description as published by the source.
Tabby (formerly Terminus) is a highly configurable terminal emulator. Prior to 1.0.233, Tabby registers itself as the handler for the tabby:// URL scheme on all platforms. The URL scheme handler supports a run command that directly executes OS commands with no user confirmation, sanitization, or sandboxing. An attacker can craft a malicious link (tabby://run?command=...) and deliver it via a website, email, chat message, or any other medium. When a victim clicks the link, the OS launches Tabby which immediately spawns the specified command as a child process with the user's full privileges. This is a zero-click-after-link-visit RCE vulnerability. This vulnerability is fixed in 1.0.233.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-45035 has been found in Tabby.
Successful exploitation can lead to full system takeover. CVSS score: 8.8/10.
What to do: upgrade Tabby to 1.0.233 or later.
If unsure, ask your IT team or search "Tabby CVE-2026-45035" on the vendor's site.
CVE-2026-45035 (Tabby) — CWE-78 / CVSS v3 8.8
Attack vector: remote (network-reachable) / 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.
OS command injection (CWE-78) exists in Tabby.
Check the vendor advisory for the affected versions of Tabby.
Severity: High (CVSS 8.8/10). Successful exploitation can lead to full system takeover.
Update to 1.0.233.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
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
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 し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade Tabby to 1.0.233ステージング環境で 1.0.233 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov