CVE-2026-114145 GitPython validates a submodule's ".git" path only after cloning into it (RCE)
- Exploited in the wild
- Not known
- Fix
- Available
What is CVE-2026-114145?
CVE-2026-114145 is a high-severity vulnerability in gitpython-developers GitPython, published on 21 Oct 2026.
Official description
GitPython is a python library used to interact with Git repositories. Prior to 3.2.1, create_submodule() in git/objects/submodule/base.py accepts an attacker-influenced submodule path such as .git/hooks and invokes _clone_repo() before safely rejecting the destination. In 3.1.x, _validate_repo_path() does not exist and the call succeeds silently, while in 3.2.0 and later affected revisions the check in git/index/base.py raises ValueError only after the clone has written to disk and does not remove the planted file. An attacker-controlled submodule can therefore place an executable post-checkout hook that a later Git operation executes. Exploitation requires an application to accept an untrusted submodule path and a clone destination such as .git/hooks that is empty enough for Git to clone into it, which commonly means that default sample hooks are absent. This issue is fixed in version 3.2.1.
Weakness: CWE-696
Which versions are affected by CVE-2026-114145?
2 open source packages ship an affected version, including Gitpython and gitpython.
| Package | Affected | Fixed in |
|---|---|---|
Gitpython PyPI | All versions | 3.2.1 |
gitpython PyPI | All versions | 3.2.1 |
How do I fix CVE-2026-114145?
Upgrade Gitpython to 3.2.1 or later.
Is CVE-2026-114145 being exploited?
There is no known exploitation of CVE-2026-114145 in the wild and no public exploit code.
Sources
Also known as CLSA-2026-1792741260, DEBIAN-CVE-2026-114145, ECHO-5e70-37df-b83d, GHSA-83vg-56qc-22m7, MINI-qvx6-jjgm-mqm5, UBUNTU-CVE-2026-114145.