OS Command Injection in Gitk (CVE-2025-27614)
Summary
OS command injection in Gitk (CVE-2025-27614). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 2.43.7 or later.
Original description
The description as published by the source.
Gitk is a Tcl/Tk based Git history browser. Starting with 2.41.0, a Git repository can be crafted in such a way that with some social engineering a user who has cloned the repository can be tricked into running any script (e.g., Bourne shell, Perl, Python, ...) supplied by the attacker by invoking gitk filename, where filename has a particular structure. The script is run with the privileges of the user. This vulnerability is fixed in 2.43.7, 2.44.4, 2.45.4, 2.46.4, 2.47.3, 2.48.2, 2.49.1, and 2.50.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
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-2025-27614 has been found in Gitk.
Successful exploitation can lead to full system takeover.
What to do: upgrade Gitk to 2.43.7 or later.
If unsure, ask your IT team or search "Gitk CVE-2025-27614" on the vendor's site.
CVE-2025-27614 (Gitk) — CWE-78
Attack vector: local / unauthenticated
Patched: 2.43.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.
OS command injection (CWE-78) exists in Gitk.
Check the vendor advisory for the affected versions of Gitk.
Severity: ?. Successful exploitation can lead to full system takeover.
Update to 2.43.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 'Gitk' . 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 'Gitk' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Gitkを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade Gitk to 2.43.7ステージング環境で 2.43.7 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Alpine Linux ALPINE-CVE-2025-27614 git Fixed in: 2.43.7-r0
- Debian DEBIAN-CVE-2025-27614 git Fixed in: 1:2.47.3-0+deb13u1
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- patch github.com
- web openwall.com