CVE-2026-67323: Improper Neutralization of Special Elements used in a Command ('Command Injection') in gitpython-developers GitPython
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.
AI Analysis
Technical Summary
GitPython before version 3.1.51 improperly neutralizes special elements in command arguments, specifically in the Repo.archive() and git.ls_remote() methods, allowing command injection via options such as --exec and --upload-pack. Furthermore, Repo.iter_commits() and Repo.blame() do not validate revision arguments that begin with a dash, which can cause Git to open and truncate arbitrary files. These vulnerabilities enable an attacker to execute arbitrary commands or manipulate files if the application using GitPython passes attacker-controlled inputs to these methods.
Potential Impact
Successful exploitation can lead to arbitrary command execution on the host running GitPython, as well as potential file truncation or modification. This can compromise system integrity and confidentiality. The vulnerabilities require local access or an application that passes attacker-controlled arguments to the affected GitPython methods.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, avoid passing untrusted or attacker-controlled input to the affected GitPython methods (Repo.archive(), git.ls_remote(), Repo.iter_commits(), and Repo.blame). Monitor vendor communications for updates and apply patches promptly once released.
CVE-2026-67323: Improper Neutralization of Special Elements used in a Command ('Command Injection') in gitpython-developers GitPython
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.
CVSS v4.0
Score 8.6high
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
GitPython before version 3.1.51 improperly neutralizes special elements in command arguments, specifically in the Repo.archive() and git.ls_remote() methods, allowing command injection via options such as --exec and --upload-pack. Furthermore, Repo.iter_commits() and Repo.blame() do not validate revision arguments that begin with a dash, which can cause Git to open and truncate arbitrary files. These vulnerabilities enable an attacker to execute arbitrary commands or manipulate files if the application using GitPython passes attacker-controlled inputs to these methods.
Potential Impact
Successful exploitation can lead to arbitrary command execution on the host running GitPython, as well as potential file truncation or modification. This can compromise system integrity and confidentiality. The vulnerabilities require local access or an application that passes attacker-controlled arguments to the affected GitPython methods.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, avoid passing untrusted or attacker-controlled input to the affected GitPython methods (Repo.archive(), git.ls_remote(), Repo.iter_commits(), and Repo.blame). Monitor vendor communications for updates and apply patches promptly once released.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- VulnCheck
- Date Reserved
- 2026-07-29T13:07:21.183Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a6deb26bf32cb7a34c1fc0d
Added to database: 08/01/2026, 12:48:38 UTC
Last enriched: 08/01/2026, 13:04:29 UTC
Last updated: 08/01/2026, 21:21:09 UTC
Views: 8
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.