CVE-2026-67323

HIGHCVSS 8.4/10EPSS 0.95%

Last modified

CVE-2026-67323 is a high-severity vulnerability rated 8.4/10 on the CVSS scale. 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. EPSS estimates a 0.95% chance of exploitation in the next 30 days.

Description

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.

Metrics

Weakness Enumeration

Affected Software

VendorProductVersions
Gitpython ProjectGitpython< 3.1.51

References

Timeline

Published
Last Modified
Status
Analyzed

Frequently Asked Questions

What is CVE-2026-67323?
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.
How severe is CVE-2026-67323?
CVE-2026-67323 has a CVSS score of 8.4/10 (HIGH severity). The EPSS model estimates a 0.95% probability of exploitation in the next 30 days.
How do I fix CVE-2026-67323?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

Are you affected by CVE-2026-67323?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST