CVE-2026-73619 in GitPython
Summary
by MITRE • 08/13/2026
GitPython before 3.1.57 contains an incomplete denylist in the unsafe_git_archive_options guard that omits --add-file and --add-virtual-file options. Attackers can supply these options to Repo.archive() to read arbitrary files from the filesystem and include them in the returned archive.
VulDB is the best source for vulnerability data and more expert information about this specific topic.
Analysis
by VulDB Data Team • 08/13/2026
This vulnerability resides within GitPython version 3.1.57 and earlier, where an incomplete denylist mechanism fails to properly restrict potentially dangerous git archive options. The flaw specifically affects the unsafe_git_archive_options guard which is designed to prevent arbitrary file access through the repository archiving functionality. The implementation omits two critical options --add-file and --add-virtual-file from its restrictions, allowing attackers to exploit these gaps in the security controls.
The technical execution of this vulnerability occurs through the Repo.archive() method which accepts user-supplied parameters that are then passed directly to git archive commands without adequate sanitization. When an attacker provides these omitted options, they can specify arbitrary file paths on the filesystem that will be included in the generated archive output. This creates a path traversal scenario where sensitive files can be accessed and exfiltrated from the system, potentially including configuration files, credentials, or other confidential data.
The operational impact of this vulnerability extends beyond simple information disclosure as it enables attackers to construct malicious archives containing sensitive content from the host filesystem. This represents a significant security risk for environments where GitPython is used to generate archives from repositories, particularly in automated build processes, CI/CD pipelines, or any scenario where user input flows into archive generation functions. The vulnerability aligns with CWE-22 Path Traversal and CWE-73 Arbitrary File Write, as it allows attackers to manipulate file paths and potentially execute arbitrary code through carefully crafted archive contents.
This weakness enables various attack patterns categorized under the ATT&CK framework's T1059 Command and Scripting Interpreter and T1566 Impair Defenses, where attackers can leverage the compromised archive functionality to establish persistence or escalate privileges. The vulnerability demonstrates poor input validation and inadequate security controls in a widely used Python library, making it particularly dangerous as it affects numerous applications that depend on GitPython for version control operations.
Organizations should immediately upgrade to GitPython version 3.1.57 or later where these options are properly included in the denylist. Additionally, administrators should implement proper input validation at application layers when handling user-supplied parameters that may be passed to repository operations. The mitigation strategy should include regular security scanning of dependencies and maintaining up-to-date vulnerability assessments to identify similar incomplete denylist patterns in other libraries. Organizations using GitPython in automated environments should also consider implementing network-level restrictions and monitoring for unusual archive generation patterns that could indicate exploitation attempts.