Is CVE-2026-110859 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-110859 being exploited in the wild.

How severe is CVE-2026-110859?

High severity, with a CVSS score of 7.5, published 14 October 2026.

Which products and versions are affected?

GitPython before 3.2.0; gitpython (PyPI) ECOSYSTEM:introduced=0,fixed=3.2.0.

Is there a fix for CVE-2026-110859?

Yes. gitpython (PyPI): upgrade to 3.2.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-110859 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-110859?

Check whether you run GitPython or gitpython (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-110859: GitPython argument injection in Head.checkout()

CVE-2026-110859 · Severity: high · CVSS 7.5 · Published 2026-10-14

GitPython is a Python library that applications use to interact with Git repositories, including cloning repositories from user-supplied URLs. An attacker can create a malicious repository with a specially crafted branch name that injects git command-line options, allowing arbitrary file reading from the system where the application runs. When a vulnerable application clones and checks out such a repository, file contents leak through error messages.

Technologies: GitPython, gitpython (PyPI). Vendors: GitPython, PyPI.

Quick answers

Is CVE-2026-110859 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-110859 being exploited in the wild.
How severe is CVE-2026-110859?: High severity, with a CVSS score of 7.5, published 14 October 2026.
Which products and versions are affected?: GitPython before 3.2.0; gitpython (PyPI) ECOSYSTEM:introduced=0,fixed=3.2.0.
Is there a fix for CVE-2026-110859?: Yes. gitpython (PyPI): upgrade to 3.2.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-110859 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-110859?: Check whether you run GitPython or gitpython (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

gitpython (PyPI): upgrade to 3.2.0 or later
```
pip install "gitpython>=3.2.0"
```

Technical details

The Head.checkout() method in git/refs/head.py passes the branch name directly to git checkout without inserting the -- argument separator, allowing injection of git options like --pathspec-from-file=/etc/passwd. The method guards **kwargs for unsafe options but ignores the positional branch name argument. An attacker with ability to host a repository (no authentication required) can trigger arbitrary file reads when a consuming application clones and checks out the default branch.

Affected products

GitPython GitPython before 3.2.0

Identifiers

CVE-2026-110859
GHSA-23mf-xhv8-69c2

Timeline

2026-09-30: disclosed
2026-10-14: advisory

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.