GitPython Command Injection and File Truncation Vulnerability

GitPython versions before 3.1.51 are susceptible to command injection and arbitrary file manipulation due to improper input validation when handling keyword arguments and revision strings. Specifically, the methods Repo.archive() and git.ls_remote() fail to sanitize keyword arguments, enabling attackers to inject dangerous Git options such as --exec or --upload-pack, which results in arbitrary command execution on the host system. Furthermore, the methods Repo.iter_commits() and Repo.blame() do not validate revision arguments for leading dashes. This allows an attacker to pass crafted strings such as --output=<path>, causing the underlying Git process to open and truncate arbitrary files on the filesystem. This vulnerability affects any application that passes untrusted user input directly into these specific GitPython method arguments.

Impact

The vulnerability allows for remote command execution and local file destruction. An attacker who can influence the inputs processed by these GitPython methods can achieve full control over the application's runtime environment or perform denial-of-service attacks by corrupting critical system or application files. This impacts any environment running software that integrates GitPython versions older than 3.1.51 for repository management or CI/CD pipeline automation.

Recommendation

• Upgrade the GitPython library to version 3.1.51 or later in all application dependencies to remediate CVE-2026-67323.
• Audit application code to identify where user-supplied input is passed as arguments to Repo.archive(), git.ls_remote(), Repo.iter_commits(), and Repo.blame().
• Implement strict input validation or allowlisting for any variables that are passed to GitPython methods to prevent the injection of flags starting with dashes.
• Review application logs for unusual process command lines triggered by Python application workers.