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

Summary

Vulnerability in python-git (UBUNTU-CVE-2026-44244). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 0.3.2~RC1-3ubuntu0.1~esm3 or later.

Original description

The description as published by the source.

GitPython is a python library used to interact with Git repositories. Prior to version 3.1.49, GitConfigParser.set_value() passes values to Python's configparser without validating for newlines. GitPython's own _write() converts embedded newlines into indented continuation lines (e.g. \n becomes \n\t), but Git still accepts an indented [core] stanza as a section header — so the injected core.hooksPath becomes effective configuration. Any Git operation that invokes hooks (commit, merge, checkout) will then execute scripts from the attacker-controlled path. This issue has been patched in version 3.1.49.

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-44244 has been found in python-git.
Successful exploitation can lead to full system takeover.
What to do: upgrade python-git to 0.3.2~~RC1-3ubuntu0.1~~esm3 or later.
If unsure, ask your IT team or search "python-git UBUNTU-CVE-2026-44244" on the vendor's site.

UBUNTU-CVE-2026-44244 (python-git)
Attack vector: local / no user interaction
Patched: 0.3.2~RC1-3ubuntu0.1~esm3 — 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 0.3.2~~RC1-3ubuntu0.1~~esm3.

🛡️ 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 0.3.2~RC1-3ubuntu0.1~esm3
```
ステージング環境で 0.3.2~~RC1-3ubuntu0.1~~esm3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
3
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Ubuntu:Pro:14.04:LTS python-git

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.3.2~RC1-3ubuntu0.1~esm3"}]}]

Ubuntu:Pro:16.04:LTS python-git

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.0.1+git137-gc8b8379-2.1ubuntu0.1~esm4"}]}]

Ubuntu:Pro:18.04:LTS python-git

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.1.8-1ubuntu0.1~esm4"}]}]

Ubuntu:Pro:20.04:LTS python-git

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.0.7-1ubuntu0.1~esm4"}]}]

Ubuntu:Pro:22.04:LTS python-git

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.1.24-1ubuntu0.1~esm3"}]}]

Ubuntu:24.04:LTS python-git