gitpython-developers GitPython up to 3.1.50 command injection

Summaryinfo

A vulnerability was found in gitpython-developers GitPython up to 3.1.50. It has been classified as critical. Affected is an unknown function. This manipulation causes command injection. This vulnerability is registered as CVE-2026-67325. Remote exploitation of the attack is possible. No exploit is available.

Detailsinfo

A vulnerability has been found in gitpython-developers GitPython up to 3.1.50 and classified as critical. Affected by this vulnerability is an unknown code block. The manipulation with an unknown input leads to a command injection vulnerability. The CWE definition for the vulnerability is CWE-77. The product constructs all or part of a command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended command when it is sent to a downstream component. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

GitPython before 3.1.51 contains an incomplete command injection blocklist that fails to account for git's long-option prefix abbreviation feature. Attackers can bypass the unsafe options guard by using abbreviated option names like upload_p instead of upload_pack, which git resolves to dangerous options and executes arbitrary commands.

The advisory is shared at github.com. This vulnerability is known as CVE-2026-67325 since 07/29/2026. The exploitation appears to be easy. The attack can be launched remotely. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1202 for this issue.

The vulnerability scanner Nessus provides a plugin with the ID 331618 (Linux Distros Unpatched Vulnerability : CVE-2026-67325), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 3.1.51 eliminates this vulnerability.

The vulnerability is also documented in the databases at Tenable (331618) and EUVD (EUVD-2026-51858). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

• Programming Language Software

Vendor

• gitpython-developers

Name

• GitPython

Version

• 3.1.0
• 3.1.1
• 3.1.2
• 3.1.3
• 3.1.4
• 3.1.5
• 3.1.6
• 3.1.7
• 3.1.8
• 3.1.9
• 3.1.10
• 3.1.11
• 3.1.12
• 3.1.13
• 3.1.14
• 3.1.15
• 3.1.16
• 3.1.17
• 3.1.18
• 3.1.19
• 3.1.20
• 3.1.21
• 3.1.22
• 3.1.23
• 3.1.24
• 3.1.25
• 3.1.26
• 3.1.27
• 3.1.28
• 3.1.29
• 3.1.30
• 3.1.31
• 3.1.32
• 3.1.33
• 3.1.34
• 3.1.35
• 3.1.36
• 3.1.37
• 3.1.38
• 3.1.39
• 3.1.40
• 3.1.41
• 3.1.42
• 3.1.43
• 3.1.44
• 3.1.45
• 3.1.46
• 3.1.47
• 3.1.48
• 3.1.49
• 3.1.50

Website

• Product: https://github.com/gitpython-developers/GitPython/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion