CVE-2026-67323

GitPython before 3.1.51, a widely used Python library for interacting with Git repositories, does not guard caller-supplied keyword arguments before building git command lines, so option-shaped values such as --exec or --upload-pack passed to Repo.archive() or git.ls_remote() are interpreted by Git itself, enabling command injection and arbitrary command execution. Additionally, Repo.iter_commits() and Repo.blame() do not check revision arguments for a leading dash, so a revision such as --output=<path> causes Git to open and truncate an arbitrary file. An attacker must be able to control arguments an application passes into these methods, and gains execution of arbitrary commands with the privileges of the Python process or destruction of arbitrary files. Any Python application or service running GitPython earlier than 3.1.51 and forwarding attacker-controlled input to these APIs is affected, while applications using only fixed, hardcoded arguments are not meaningfully exposed. No in-the-wild exploitation is confirmed (not in CISA KEV, EPSS about 1%), but public advisories and proof-of-concept references are available.

What to do: Upgrade to GitPython 3.1.51 or later. As an interim mitigation, validate or sanitize any attacker-controlled values before they reach Repo.archive(), git.ls_remote(), Repo.iter_commits() or Repo.blame(), rejecting arguments that begin with a dash (e.g., --exec, --upload-pack, --output=). Audit code paths where user input flows into these APIs to confirm whether your deployment is actually exposed.