External risk intelligence

GitPython Remote Pull Refspec Command Injection.

CVE advisorySeverity: CRITICAL (CVSS 9.2)

CVE-2026-110858

GitPython is a library used by developers to interact with Git repositories within applications. While it processes network-based data via local-path or SSH transports, it is typically an internal component of a larger software application rather than a public-facing edge service or standalone network appliance, making direct internet exposure of this specific library function uncommon.

Remote Code Execution

Halo Surface Signal: 2 out of 5 — less likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A remote code execution vulnerability exists in a widely used Python library for interacting with Git. This issue allows attackers to potentially run unauthorized commands on affected systems when specific Git operations are performed with crafted input. The main concern is confirming relevance and exposure.

A code flaw lets attackers run commands on your systems.
It's used in many applications, so widespread impact is possible.
Verify if this library is in use and if it's exposed.

Attack Path

How an attacker could exploit the issue

An attacker could exploit this vulnerability by controlling a refspec during a Git pull operation. This allows them to insert operating system commands that are then executed with the privileges of the user running the GitPython code. This can occur over local-path or SSH connections.

Unauthenticated access to a vulnerable GitPython function.
Controlling refspec during a Git pull operation.
Arbitrary operating system command execution.

Live Threat

Current exploitation, exposure, and threat context

When supported by the advisory, attackers controlling the refspec in GitPython's `Remote.pull()` function could execute arbitrary operating system commands as the calling process. This could occur over local-path or SSH transports when an attacker can influence the refspec argument.

Execution of arbitrary OS commands.
Refspec controlled via function arguments.
Compromise of the calling process.

Operational Fix

Recommended remediation, mitigation, and detection steps

Application and platform teams are likely responsible for addressing this vulnerability, as GitPython is a library integrated into custom or internal applications. The first practical step is to identify all systems using the affected library, confirm their exposure and business criticality, and then determine the accountable owner for remediation planning.

Ownership rests with application/platform teams.
Verify affected systems and exposure first.
Plan remediation based on risk assessment.

Supplementary metadata

CVSS vector

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Free EASM Trial See How Signal Works

Frequently asked questions

What is GitPython and what do developers use it for?

GitPython is a Python library that enables software to interact with Git repositories programmatically. Developers integrate it into applications to automate tasks like cloning, pulling, and managing version control data. Because it acts as an interface between code and Git, it is a backend dependency embedded within larger software projects rather than a standalone application.

How does CVE-2026-110858 lead to command injection?

This vulnerability is classified as CWE-88: Argument Injection or Modification. The library attempts to secure its Remote.pull() function by filtering options, but it fails to sanitize the positional 'refspec' argument. An attacker can use this gap to inject malicious OS commands, which the system then executes with the same permissions as the application running the GitPython library.

What triggers this vulnerability in GitPython?

The vulnerability is triggered when the Remote.pull() function is called while an attacker has control over the refspec input. It specifically affects operations using local-path or SSH transports. Importantly, the flaw is not triggered if the refspec is hardcoded or comes from a trusted, non-user-controlled source, as the attacker must be able to inject the specific command-line arguments.

Who should be concerned about this vulnerability?

Teams maintaining applications that process external Git data using GitPython should investigate their implementation. According to Halo Surface Signal, this library is typically an internal component, making direct internet exposure via this specific function uncommon. However, you should care if your software accepts user-provided inputs that eventually reach a Git pull operation.

What are the first steps to address this GitPython issue?

Begin by identifying which applications in your environment rely on GitPython versions 3.1.30 through 3.1.x. Once identified, evaluate whether those applications allow untrusted users to influence the refspec argument in Git operations. Finally, coordinate with your application owners to plan an update to a non-vulnerable version, ensuring the library remains a manageable dependency in your software stack.

References

Written by Nicholas Merritt

Nicholas Merritt is VP of Security Solutions at Halo Security. With more than 25 years across application security, vulnerability prioritization, and offensive security, he helps teams translate threat data into practical exposure validation and remediation focus. He authors Halo Threat Intelligence CVE advisories using Halo Surface Signal and H/A/L/O context to prioritize internet-facing risk.