Vulnerability in python-git (UBUNTU-CVE-2026-67324)

Summary

Vulnerability in python-git (UBUNTU-CVE-2026-67324). 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.

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: OSV.dev (Open Source Vulnerabilities) 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 UBUNTU-CVE-2026-67324 has been found in python-git.
Successful exploitation can lead to full system takeover.
What to do: upgrade python-git to 3.1.51 or later.
If unsure, ask your IT team or search "python-git UBUNTU-CVE-2026-67324" on the vendor's site.

UBUNTU-CVE-2026-67324 (python-git)
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.

❓ What is the problem

A vulnerability (unclassified) exists in python-git.

📍 Affected scope

Check the vendor advisory for the affected versions of python-git.

🔥 Severity

Severity: ?. Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 3.1.51.

🛡️ 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 'python-git' . 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

1
Identify exposure identify
```
grep -r 'python-git' . | grep -v node_modules
```
リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で python-git を grep し、稼働しているサービス・バージョンを把握する。
2
Apply patch patch
```
Upgrade python-git to 3.1.51
```
ステージング環境で 3.1.51 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
3
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。