Code Injection in GitPython (CVE-2026-44244)
Summary
Code injection in GitPython (CVE-2026-44244). Successful exploitation can lead to full system takeover. Exploitable via configparser. Mitigation: upgrade to 3.1.49 or later.
Original description
The description as published by the source.
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.
The vulnerability is not merely malformed config output: GitPython's own writer converts embedded newlines into indented continuation lines, but Git still accepts an indented [core] stanza as a section header, so the injected core.hooksPath becomes effective configuration.
This was found while auditing MLRun's project.push() method, which passes author_name and author_email directly to config_writer().set_value() with no sanitization. Both parameters cross a trust boundary — they are caller-supplied API inputs that end up in .git/config.
PoC (standalone, no MLRun required):
import git, subprocess, os
repo = git.Repo("/tmp/testrepo")
with repo.config_writer() as cw:
cw.set_value("user", "name", "foo\n[core]\nhooksPath=/tmp/hooks")
r = subprocess.run(["git", "config", "core.hooksPath"], cwd="/tmp/testrepo", capture_output=True, text=True)
assert r.returncode == 0
print(r.stdout.strip()) # /tmp/hooks
os.makedirs("/tmp/hooks", exist_ok=True)
open("/tmp/hooks/pre-commit",…
Source: GitHub Security Advisories (Global) 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 CVE-2026-44244 has been found in GitPython.
Attackers can target a specific entry point like configparser over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 7.8/10.
What to do: upgrade GitPython to 3.1.49 or later.
If unsure, ask your IT team or search "GitPython CVE-2026-44244" on the vendor's site.
CVE-2026-44244 (GitPython) — CWE-94 / CVSS v3 7.8
Attack vector: local / no user interaction
Attack surface: configparser / core.hooksPath / author_name / author_email
Patched: 3.1.49 — 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.
Arbitrary code execution (CWE-94) exists in GitPython. Attackers reach the vulnerable code path via configparser.
Check the vendor advisory for the affected versions of GitPython. Attack surface: configparser / core.hooksPath / author_name / author_email.
Severity: High (CVSS 7.8/10). Successful exploitation can lead to full system takeover.
Update to 3.1.49.
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.49ステージング環境で 3.1.49 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
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-44244 python-git
- Ubuntu UBUNTU-CVE-2026-44244 python-git Fixed in: 0.3.2~RC1-3ubuntu0.1~esm3
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web github.com