Code Injection in GitButler (CVE-2026-45261)
Summary
Code injection in GitButler (CVE-2026-45261). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 0.19.7 or later.
Original description
The description as published by the source.
GitButler is a modern Git-based version control interface for AI-powered workflows. Prior to 0.19.7, a emote code execution vulnerability exists in the Tauri-based GitButler desktop application. An attacker can inject a malicious link in a pull request body, which if clicked by the user allows for arbitrary script execution in the Tauri webview. Users that have not enabled forge integration are not at risk. This vulnerability is fixed in 0.19.7.
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-45261 has been found in GitButler.
Risk of unauthorized operations or information disclosure.
What to do: upgrade GitButler to 0.19.7 or later.
If unsure, ask your IT team or search "GitButler CVE-2026-45261" on the vendor's site.
CVE-2026-45261 (GitButler) — CWE-94
Patched: 0.19.7 — 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.
Arbitrary code execution (CWE-94) exists in GitButler.
Check the vendor advisory for the affected versions of GitButler.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 0.19.7.
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 'GitButler' . 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 'GitButler' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
GitButlerを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade GitButler to 0.19.7ステージング環境で 0.19.7 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov