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.
References
| Link | Resource |
|---|---|
| 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 |
Configurations
History
No history.
Information
Published : 2026-08-01 13:17
Updated : 2026-09-03 16:11
NVD link : CVE-2026-67323
Mitre link : CVE-2026-67323
CVE.ORG link : CVE-2026-67323
JSON object : View
Products Affected
gitpython_project
- gitpython
CWE
CWE-77
Improper Neutralization of Special Elements used in a Command ('Command Injection')
