CVE-2026-67323: GitPython before 3.1.51 Command Injection via unguarded Git options
GitPython before 3.1.51 fails to guard against dangerous Git options passed as keyword arguments in Repo.archive() and git.lsremote(), allowing command injection via options such as --exec/--upload-pack (leading to arbitrary command execution). Additionally, Repo.itercommits() 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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/python-gitto a version that resolves this vulnerability.Fixed in 3.1.30-1+deb12u3 - Upgrade
Upgrade
debian/python-gitto a version that resolves this vulnerability.Fixed in 3.1.44-1+deb13u1 - Upgrade
Upgrade
debian/python-gitto a version that resolves this vulnerability.Fixed in 3.1.61-1 - Upgrade
Upgrade
debian/python-gitto a version that resolves this vulnerability.Fixed in 3.1.30-1+deb12u3Fixed in 3.1.44-1+deb13u1Fixed in 3.2.1-1
Event History
Frequently Asked Questions
What is the severity of CVE-2026-67323?
The severity of CVE-2026-67323 is rated high with a score of 8.4.
How do I fix CVE-2026-67323?
To mitigate CVE-2026-67323, upgrade GitPython to version 3.1.51 or later.
What type of vulnerability is CVE-2026-67323?
CVE-2026-67323 is classified as a command injection vulnerability.
What functions are affected by CVE-2026-67323?
CVE-2026-67323 affects Repo.archive(), git.ls_remote(), Repo.iter_commits(), and Repo.blame() functions.
What are the potential impacts of CVE-2026-67323?
Exploitation of CVE-2026-67323 can lead to arbitrary command execution on the host system.