CVE-2026-67323: GitPython before 3.1.51 Command Injection via unguarded Git options
gitpython-developers · GitPython
Fixed in 3.1.51 · Affected: gitpython-developers before 3.1.51 · Exploitation: possible (1 to 10%)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 69% of scored CVEs
DescriptionCVE.org
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.
Affected products1
From the CVE record. A product or version that is not listed is unknown, not unaffected.
- gitpython-developers · GitPythonbefore 3.1.51
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
- Exploitation
- Possible (1 to 10%). EPSS between 1% and 10%.
- CISA KEV
- Not listed
- Public check
- No public nuclei template
- Vendor
- gitpython-developers
- Published
- August 2026
CoverageNo articles yet
No CyberSIXT article names CVE-2026-67323 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.