top of page
perceptive_background_267k.jpg

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 injecti…

Published:

1 August 2026 at 00:00:00

Alert date:

1 August 2026 at 16:10:43

Source:

nvd.nist.gov

Click to open the original link from this advisory

Supply Chain & Dependencies, Web Technologies, Zero-Day Vulnerabilities

GitPython versions before 3.1.51 contain multiple security vulnerabilities allowing command injection and arbitrary file manipulation. The library fails to guard against dangerous Git options passed as keyword arguments in Repo.archive() and git.ls_remote(), enabling command injection via options like --exec and --upload-pack that can lead to arbitrary command execution. Additionally, Repo.iter_commits() and Repo.blame() do not validate leading-dash revision arguments, allowing a crafted revision such as --output=<path> to cause Git to open and truncate arbitrary files on the system. Exploitation requires that an application passes attacker-controlled arguments to these vulnerable methods. The vulnerability affects any application built on GitPython that processes untrusted user input and forwards it to these APIs. Users are advised to upgrade to GitPython 3.1.51 or later to remediate these issues.

Technical details

Mitigation steps:

Affected products:

GitPython
GitPython before 3.1.51

Related links:

Related CVE's:

Related threat actors:

IOC's:

This article was created with the assistance of AI technology by Perceptive.

© 2025 by Perceptive Security. All rights reserved.

email: info@perceptivesecurity.com

Disclaimer: Deze website toont informatie afkomstig van externe bronnen. Perceptive aanvaardt geen verantwoordelijkheid voor de inhoud, juistheid of volledigheid van deze informatie.

bottom of page