CVE-2026-67323

published 1 Aug 2026 · updated 8 Oct 2026

GitPython before 3.1.51 Command Injection via unguarded Git options

8.4HighCVSS 8.4EPSS 1%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. Fixed in 3.1.51.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
gitpython-developers<3.1.513.1.51

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-67323 severity on Zeptric[![CVE-2026-67323](https://zeptric.io/badge/cve/CVE-2026-67323.svg)](https://zeptric.io/cve/CVE-2026-67323)