CVE-2026-110859VulnerabilityPublished 14 Oct 2026Updated 28 Oct 2026

Python git: GitPython before 3.2.0 contains an argument injection vulnerability in Head.checkout() that allows remote

Affects python-gitSource GCVE Database

Authoritative record:CVE-2026-110859· High 8.7

Not known to be exploited · CVSS 8.7 High.

Data as of 28 Oct 2026, 23:29 UTC

CVSS 4.0 base score

8.7High

How severe the flaw is on the 0–10 CVSS scale.

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: High
Vulnerable system integrity: None
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: High: There is a total loss of confidentiality, resulting in all information within the Vulnerable System being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact. For example, an attacker steals the administrator's password, or private encryption keys of a web server.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 14 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Ubuntu 26.10python-git`pkg:deb/ubuntu/python-git?arch=source&distro=stonking`Other threats	Affected =3.1.46-1 =3.1.50-1 =3.1.61-1	Fixed in–
Ubuntu Pro 26.04 LTSpython-git`pkg:deb/ubuntu/python-git?arch=source&distro=esm-apps/resolute`Other threats	Affected 3.1.44-1 – 3.1.46-1ubuntu0.1~esm1 4 affected builds	Fixed in–
Ubuntu Pro 24.04 LTSpython-git`pkg:deb/ubuntu/python-git?arch=source&distro=esm-apps/noble`Other threats	Affected 3.1.30-1 – 3.1.37-3ubuntu0.1~esm2 4 affected builds	Fixed in–
Ubuntu Pro 22.04 LTSpython-git`pkg:deb/ubuntu/python-git?arch=source&distro=esm-apps/jammy`Other threats	Affected 3.1.14-1 – 3.1.24-1ubuntu0.1~esm3 6 affected builds	Fixed in–
Ubuntu Pro 20.04 LTSpython-git`pkg:deb/ubuntu/python-git?arch=source&distro=esm-apps/focal`Other threats	Affected 2.1.11-1 – 3.0.7-1ubuntu0.1~esm4 7 affected builds	Fixed in–
Ubuntu Pro 18.04 LTSpython-git`pkg:deb/ubuntu/python-git?arch=source&distro=esm-apps/bionic`Other threats	Affected 2.1.5-1 – 2.1.8-1ubuntu0.1~esm4 7 affected builds	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Users and administrators should upgrade GitPython to version 3.2.0 or later, where this vulnerability is fixed. There are no indications that this vulnerability is mitigated by configuration or that no action is required. No known exploits are reported in the wild at this time.

Description

GitPython versions before 3.2.0 have an argument injection vulnerability in the Head.checkout() method. This flaw allows remote attackers to read arbitrary files by supplying a specially crafted branch name that is interpreted as a git option. Specifically, an attacker can host a repository with a default branch named --pathspec-from-file=<path>, causing applications that clone and check out the active branch to leak file contents via GitCommandError messages.

Impact

An attacker can cause applications using vulnerable GitPython versions to disclose arbitrary file contents remotely. This information disclosure occurs during the checkout of a maliciously named branch, potentially exposing sensitive data from the victim's environment. The vulnerability does not impact integrity or availability but has a high confidentiality impact.

Summary

GitPython prior to version 3.2.0 contains an argument injection vulnerability in the Head.checkout() function. The vulnerability arises because the branch name is parsed as a git command option, enabling an attacker to craft a branch name such as --pathspec-from-file=<path>. When a cloning application checks out this branch, it inadvertently leaks the contents of arbitrary files through error messages generated by GitCommandError. This issue affects multiple specific versions of python-git as listed, and has a CVSS 3.1 score of 7.5, indicating a high severity remote code injection risk with no privileges required and no user interaction needed.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 28 Oct 2026, 23:29 UTC

Technical details

References

Community reviews

Related threats