OS Command Injection in gitpython (GHSA-cw2r-r7mw-j3hc)
Summary
OS command injection in gitpython (GHSA-cw2r-r7mw-j3hc). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 3.1.51 or later.
Original description
The description as published by the source.
Duplicate Advisory
This advisory has been withdrawn because it is a duplicate of GHSA-v396-v7q4-x2qj. This link is maintained to preserve external references.
Original Description
GitPython 3.1.50 fails to recognize joined short-option forms such as -u (the short form of --upload-pack=) when enforcing its default unsafe-option gate. When an application passes attacker-influenced clone options into Repo.clone_from(..., multi_options=..., allow_unsafe_options=False), an attacker can supply -u to bypass the gate that blocks --upload-pack/-u, causing Git to execute the specified helper command during clone. Fixed in 3.1.51.
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 GHSA-cw2r-r7mw-j3hc has been found in gitpython.
Successful exploitation can lead to full system takeover. CVSS score: 9.8/10.
What to do: upgrade gitpython to 3.1.51 or later.
If unsure, ask your IT team or search "gitpython GHSA-cw2r-r7mw-j3hc" on the vendor's site.
GHSA-cw2r-r7mw-j3hc (gitpython) — CWE-78 / CVSS v3 9.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 3.1.51 — 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 gitpython.
Check the vendor advisory for the affected versions of gitpython.
Severity: Critical (CVSS 9.8/10). Successful exploitation can lead to full system takeover.
Update to 3.1.51.
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 'gitpython' . 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 'gitpython' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
gitpythonを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade gitpython to 3.1.51ステージング環境で 3.1.51 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2026-67324 python-git
- Ubuntu UBUNTU-CVE-2026-67324 python-git
References
- advisory nvd.nist.gov
- web github.com
- web vulncheck.com
- web github.com