CVE-2026-67323

GitPython before 3.1.51 Command Injection via unguarded Git options

Published Aug 1, 2026 CVSS 4.0 · 8.6 High EPSS 1.3% KEV · Not listed

Description

GitPython before 3.1.51 fails to guard against dangerous Git options passed as keyword arguments in Repo.archive() and git.ls_remote(), allowing command injection via options such as --exec/--upload-pack (leading to arbitrary command execution). Additionally, Repo.iter_commits() and Repo.blame() do not check for leading-dash revision arguments, so a revision like --output=<path> can cause Git to open and truncate an arbitrary file. Exploitation requires an application that passes attacker-controlled arguments to these methods.

Analysis

Technical impact

GitPython versions earlier than 3.1.51 allow an attacker to inject arbitrary Git options when calling Repo.archive() or git.ls_remote(), passing options such as --exec or --upload-pack directly to the Git binary and yielding command execution. The methods Repo.iter_commits() and Repo.blame() also fail to reject leading-dash revision arguments, so a revision like --output=<path> can cause Git to create or truncate a file at an attacker‑controlled location, enabling data loss or tampering. This vulnerability is a command injection flaw (CWE‑77, CWE‑88).

Affected Systems

The vulnerability affects the GitPython project distributed by the gitpython‑developers. Versions before 3.1.51 are vulnerable; no other vendor or product details are listed.

Risk and Exploitability

The CVSS score of 8.6 indicates high severity, and the vulnerability is not listed in the CISA KEV catalog. Exploitation requires an application that forwards untrusted arguments to the affected methods, making the attack vector an application‑level privilege escalation that can lead to arbitrary command execution. The EPSS score of 1% indicates a low but non‑zero probability of exploitation, suggesting that while the vulnerability is serious, it is unlikely to be widely exploited at the time of analysis. This vulnerability is a command injection flaw (CWE‑77, CWE‑88).

Affected Products

Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).

Vendor Product Default status Versions

gitpython-developers

GitPython

unaffected

Version	Status	Constraints
`0`	affected	< 3.1.51
`3.1.51`	unaffected	—

Configuration 1 [-]

cpe:2.3:a:gitpython_project:gitpython:*:*:*:*:*:python:*:*

No data.

Vendor Product Versions

Gitpython-developers

Gitpython

Version	Status	Scheme	Platform
`[0,3.1.51)`	affected	semver	—
`3.1.51`	unaffected	semver	—

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

Upgrade to GitPython 3.1.51 or newer, which validates and sanitizes Git options in all affected methods.
Verify that any arguments passed to Repo.archive(), git.ls_remote(), Repo.iter_commits(), and Repo.blame() do not originate from user‑controlled input or other untrusted sources.
If the application must use dangerous Git options such as --exec or --upload-pack, limit their use by configuring Git to run in a sandboxed environment or by restricting file system permissions to prevent unintended file creation or truncation.

Generated by OpenCVE AI on August 4, 2026 at 11:14 UTC.

Tracking

Advisories

Source	ID	Title
Debian DLA	DLA-4872-1	python-git security update
Github GHSA	GHSA-956x-8gvw-wg5v	GitPython: command injection via unguarded Git options in `Repo.archive()`, `git.ls_remote()`, and arbitrary file overwrite via `Repo.iter_commits()` / `Repo.blame()`

Metrics

Attack Vector Local

Attack Complexity Low

Privileges Required None

Attack Requirements None

User Interaction None

Vulnerable System Confidentiality Impact High

Vulnerable System Integrity Impact High

Vulnerable System Availability Impact High

Subsequent System Confidentiality Impact None

Subsequent System Integrity Impact None

Subsequent System Availability Impact None

Attack Vector Local

Attack Complexity Low

Privileges Required None

Scope Unchanged

Confidentiality Impact High

Integrity Impact High

Availability Impact High

User Interaction None

No CVSS v3.0

No CVSS v2

This CVE is not in the KEV list.

Exploit prediction score: 1.3% (1.251% probability within 30 days)

Exploitation poc

Automatable no

Technical Impact total

References

Link	Providers
https://github.com/gitpython-developers/GitPython/security/advisories/GHSA-956x-8gvw-wg5v
https://nvd.nist.gov/vuln/detail/CVE-2026-67323
https://www.cve.org/CVERecord?id=CVE-2026-67323
https://www.vulncheck.com/advisories/gitpython-before-command-injection-via-unguarded-git-options

History

Aug 14, 2026 5:15 PM First appearance in the feed. Affected versions updated. Affected vendors updated View changes

Type	Values Removed	Values Added
First Time appeared		Gitpython Project Gitpython Project gitpython
CPEs		cpe:2.3:a:gitpython_project:gitpython::::::python::*
Vendors & Products		Gitpython Project Gitpython Project gitpython

Aug 4, 2026 12:15 AM Weaknesses updated. Added references. Scoring metrics updated View changes

Type	Values Removed	Values Added
Weaknesses		CWE-88
References		https://nvd.nist.gov/vuln/detail/CVE-2026-67323 https://www.cve.org/CVERecord?id=CVE-2026-67323
Metrics	threat_severity `None`	threat_severity `Important`

Aug 3, 2026 9:30 PM Scoring metrics updated View changes

Type	Values Removed	Values Added
Metrics		ssvc `{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'total'}, 'version': '2.0.3'}`

Aug 2, 2026 9:00 PM First appearance in the feed. Affected vendors updated View changes

Type	Values Removed	Values Added
First Time appeared		Gitpython-developers Gitpython-developers gitpython
Vendors & Products		Gitpython-developers Gitpython-developers gitpython

Aug 1, 2026 12:45 PM Description updated. Title updated. Weaknesses updated. Added references. Scoring metrics updated View changes

Type	Values Removed	Values Added
Description		GitPython before 3.1.51 fails to guard against dangerous Git options passed as keyword arguments in Repo.archive() and git.ls_remote(), allowing command injection via options such as --exec/--upload-pack (leading to arbitrary command execution). Additionally, Repo.iter_commits() and Repo.blame() do not check for leading-dash revision arguments, so a revision like --output=<path> can cause Git to open and truncate an arbitrary file. Exploitation requires an application that passes attacker-controlled arguments to these methods.
Title		GitPython before 3.1.51 Command Injection via unguarded Git options
Weaknesses		CWE-77
References		https://github.com/gitpython-developers/GitPython/security/advisories/GHSA-956x-8gvw-wg5v https://www.vulncheck.com/advisories/gitpython-before-command-injection-via-unguarded-git-options
Metrics		cvssV3_1 `{'score': 8.4, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H'}` cvssV4_0 `{'score': 8.6, 'vector': 'CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N'}`

Subscriptions

Gitpython-developers Gitpython

Gitpython Project Gitpython

Weaknesses

CWE-77
Improper Neutralization of Special Elements used in a Command ('Command Injection')
CWE-88
Improper Neutralization of Argument Delimiters in a Command ('Argument Injection')