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.
Fix
Patch, vendor advisory and mitigation references on NVD 2
- https://github.com/gitpython-developers/GitPython/security/advisories/GHSA-956x-8gvw-wg5v Exploit, Vendor Advisory
- https://github.com/gitpython-developers/GitPython/security/advisories/GHSA-956x-8gvw-wg5v Exploit, Vendor Advisory
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 8.6 · gitpython_projectNVD modified 2026-10-23 23:10
Affected (CPE criteria) 1
cpe:2.3:a:gitpython_project:gitpython:*:*:*:*:*:python:*:*
References 3
- https://github.com/gitpython-developers/GitPython/security/advisories/GHSA-956x-8gvw-wg5v Exploit, Vendor Advisory
- https://www.vulncheck.com/advisories/gitpython-before-command-injection-via-unguarded-git-options Third Party Advisory, Exploit
- https://github.com/gitpython-developers/GitPython/security/advisories/GHSA-956x-8gvw-wg5v Exploit, Vendor Advisory