CVE-2026-67323
Received Received - Intake

GitPython Command Injection and Path Traversal Vulnerabilities

Vulnerability report for CVE-2026-67323, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-08-01

Last updated on: 2026-08-01

Assigner: VulnCheck

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 Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-01
Last Modified
2026-08-01
Generated
2026-08-01
AI Q&A
2026-08-01
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
gitpython gitpython to 3.1.51 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-77 The product constructs all or part of a command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended command when it is sent to a downstream component.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

GitPython before 3.1.51 has a command injection vulnerability in Repo.archive() and git.ls_remote() due to unsafe handling of Git options passed as arguments. Attackers can exploit options like --exec or --upload-pack to execute arbitrary commands. Additionally, Repo.iter_commits() and Repo.blame() do not validate revision arguments, allowing attackers to pass values like --output= to overwrite files.

Impact Analysis

If you use GitPython in an application that accepts user-controlled inputs for these methods, attackers could execute arbitrary commands on your system or overwrite sensitive files. This could lead to data theft, system compromise, or denial of service.

Compliance Impact

This vulnerability could lead to unauthorized data access or modification, violating GDPR's integrity and confidentiality requirements or HIPAA's safeguards for protected health information. Organizations may face compliance violations if exploited.

Mitigation Strategies

Upgrade GitPython to version 3.1.51 or later to address the command injection and file truncation vulnerabilities. Review applications using GitPython to ensure no attacker-controlled arguments are passed to vulnerable methods like Repo.archive(), git.ls_remote(), Repo.iter_commits(), or Repo.blame().

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-67323. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart