External risk intelligence

GitPython Clone Command Injection

CVE advisorySeverity: CRITICAL (CVSS 9.3)

CVE-2026-67324

GitPython is a library used by developers to integrate Git functionality into applications. While it processes data that could be influenced by external users, it is not an internet-facing service, gateway, or edge portal. Public exposure depends entirely on how a specific application implements the library, making direct public-internet reachability uncommon.

OS Command Injection

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

This advisory concerns a vulnerability in GitPython, a tool that developers use to integrate Git operations into applications. The flaw could allow an attacker to execute commands on a system during the cloning process by manipulating how certain commands are passed to Git. The primary concern is confirming whether any internal applications utilize this library in a way that could be exposed.

Attackers can trick GitPython into running commands.
Matters if your software uses GitPython for code operations.
Confirm if this library is used and how it's configured.

Attack Path

How an attacker could exploit the issue

An attacker can exploit this vulnerability by tricking an application that uses GitPython into cloning a repository with specially crafted options. When the application processes these options without proper validation, it can allow Git to execute arbitrary commands on the system.

No authentication required.
Malicious clone options.
Arbitrary command execution.

Live Threat

Current exploitation, exposure, and threat context

When applications use GitPython to clone repositories with attacker-controlled options, a vulnerability could allow the execution of arbitrary commands on the host system during the cloning process. This occurs when specific unsafe clone options are passed in a malformed way that bypasses security checks.

Arbitrary command execution on the host.
Exploitation via crafted clone options.
Compromise of the host system.

Operational Fix

Recommended remediation, mitigation, and detection steps

Application owners are likely responsible for addressing this vulnerability in GitPython, as it affects how applications interact with Git repositories. The first practical step is to identify all applications utilizing GitPython, confirm their exposure and business criticality, and then determine the accountable owner to plan for remediation.

Application owners should own the issue.
Verify all GitPython deployments.
Plan remediation based on risk.

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 how is it used?

GitPython is a Python library that enables developers to programmatically interact with Git repositories. It is commonly used within applications to automate tasks like cloning, committing, or pushing code, effectively allowing software to manage version control operations without requiring the standard Git command-line interface.

What is the vulnerability in CVE-2026-67324?

This vulnerability is an instance of CWE-78, or OS Command Injection. The library contains a flaw in its safety gate designed to block dangerous options during Git repository cloning. Because it fails to recognize shorthand command syntax, an attacker can bypass the security filter and force the underlying system to execute unauthorized commands.

How can an attacker trigger this vulnerability?

An attacker triggers the issue by supplying a specially crafted command, specifically using a joined short-option format like -u instead of the blocked --upload-pack. If an application passes user-provided data directly to GitPython's clone function, the library's gate will fail to stop the malicious command. Note that simply using GitPython is not enough; the application must be accepting and processing untrusted input as clone options.

Is my application at risk from this CVE?

Risk depends on whether your custom applications accept user input to perform repository cloning. According to Halo Surface Signal, GitPython is a library, not a standalone network service, so it is rarely directly exposed to the internet. You are primarily at risk if your application acts as an interface that allows users to supply options for Git operations.

How do I address this GitPython security issue?

First, locate all internal software components that use GitPython to perform cloning operations. Once identified, verify if those components accept user-influenced options. If they do, update the GitPython dependency to version 3.1.51 or later, which contains the fix for the command injection flaw.

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.