CVE-2026-44244·Python vulnerability
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.
- Severity
- high
- Software
- Python
- Fixed in
- 3.1.49
- Published
- 2026-05-07
Affected versions
Until: 3.1.49
Fixed in: 3.1.49
How to fix this CVE
Update GitPython to version 3.1.49 or later to patch a configuration injection vulnerability that allows arbitrary Git hook execution. The vulnerability exists in GitConfigParser.set_value(), which fails to sanitize newline characters before writing to Git configuration files. Attackers can exploit this to inject malicious hook paths that execute during Git operations like commit, merge, and checkout. Apply the update immediately across all systems running affected versions of GitPython.
sudo dnf update python3-gitDefensia detects this vulnerability
How to check if you are affected
- Step 1: Check installed GitPython version with: python3 -c "import git; print(git.__version__)"
- Step 2: List all Git repositories on the system with: find / -name '.git' -type d 2>/dev/null | head -20
- Step 3: Inspect Git config files for suspicious [core] stanza injections: grep -r "\[core\]" ~/.gitconfig /etc/gitconfig 2>/dev/null
- Step 4: Verify the patch by confirming GitPython version is 3.1.49+ and review git hooks in affected repos: ls -la .git/hooks/
FAQ
What is CVE-2026-44244?
CVE-2026-44244 is a configuration injection vulnerability in GitPython's GitConfigParser that allows attackers to inject newline characters into Git configuration values. By exploiting this flaw, an attacker can inject a malicious [core] section into the Git config, redirecting the hooksPath to an attacker-controlled directory and achieving arbitrary code execution during Git operations.
Is CVE-2026-44244 being actively exploited?
No, CVE-2026-44244 is not currently listed on the CISA Known Exploited Vulnerabilities (KEV) catalog, and no public exploits are available. However, the vulnerability's severity warrants prompt patching as exploitation requires only local access and knowledge of repository operations.
What versions of GitPython are affected by CVE-2026-44244?
All versions of GitPython prior to 3.1.49 are affected. The vulnerability was introduced in earlier versions and patched in GitPython 3.1.49 and later.
How do I check if my server is vulnerable to CVE-2026-44244?
Run: python3 -c "import git; print(git.__version__)" — if the output is less than 3.1.49, your installation is vulnerable. Additionally, check for unusual .gitconfig files with: cat ~/.gitconfig | grep -A 5 \"\[core\]\".
Does Defensia detect CVE-2026-44244?
Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If GitPython or Python is installed on a monitored server, CVE-2026-44244 will appear in your dashboard with remediation steps and affected repository inventory.
Related Python CVEs
References
Track CVEs across your fleet automatically
Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2026-44244. Free for 1 server.
Get started free