← Back
CVE-2026-42215
high
CVSS 8.8
OS Command Injection in GitPython (CVE-2026-42215)
Summary
OS command injection in GitPython (CVE-2026-42215). Successful exploitation can lead to full system takeover. Exploitable via ``upload_pack``. Mitigation: upgrade to `3.1.47` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-42215** has been found in GitPython.
Attackers can target a specific entry point like ``upload_pack`` over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 8.8/10.
What to do: upgrade GitPython to **3.1.47** or later.
If unsure, ask your IT team or search "GitPython CVE-2026-42215" on the vendor's site.
CVE-2026-42215 (GitPython) — CWE-78 / CVSS v3 8.8
Attack vector: remote (network-reachable) / no user interaction
Attack surface: `upload_pack` / `receive_pack` / `allow_unsafe_options` / `False`
Patched: `3.1.47` — 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 GitPython. Attackers reach the vulnerable code path via ``upload_pack`` without authentication.
📍 Affected scope
GitPython — . Attack surface: `upload_pack` / `receive_pack` / `allow_unsafe_options` / `False`.
🔥 Severity
Severity: High (CVSS 8.8/10). Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **3.1.47**.
🛡️ 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 'GitPython' .` 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 'GitPython' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `GitPython` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade GitPython to 3.1.47ステージング環境で 3.1.47 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
pip
GitPython
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.1.47"}]}]