CVE-2026-73619
Received Received - Intake

GitPython Archive Options Path Traversal Vulnerability

Publication date: 2026-08-13

Last updated on: 2026-08-13

Assigner: VulnCheck

Description
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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-13
Last Modified
2026-08-13
Generated
2026-08-13
AI Q&A
2026-08-13
EPSS Evaluated
N/A
NVD
CVE-2026-73619
EUVD
EUVD-2026-57823

Affected Vendors & Products

Showing 2 associated CPEs
Vendor Product Version / Range
gitpython gitpython to 3.1.57 (exc)
gitpython_developers gitpython to 3.1.57 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-73 The product allows user input to control or influence paths or file names that are used in filesystem operations.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

GitPython before version 3.1.57 has an incomplete denylist in the unsafe_git_archive_options guard. This denylist fails to block the --add-file and --add-virtual-file options, allowing attackers to read arbitrary files from the filesystem by including them in an archive generated via Repo.archive().

Detection Guidance

To detect this vulnerability, check if your system uses GitPython versions before 3.1.57. Run: pip show gitpython. If installed, verify version with: python -c "import git; print(git.__version__)". Inspect applications using Repo.archive() for user-controlled options passed to it.

Impact Analysis

If you use GitPython versions before 3.1.57, an attacker with access to the Repo.archive() method could exploit this to read sensitive files on your system that the application can access. This could lead to unauthorized data exposure or leakage of confidential information.

Compliance Impact

This vulnerability could lead to unauthorized access to sensitive data, which may violate GDPR's data protection principles or HIPAA's requirements for safeguarding protected health information. Organizations using vulnerable GitPython versions may face compliance violations if such data is exposed.

Mitigation Strategies

Upgrade GitPython to version 3.1.57 or later immediately. If upgrading is not possible, review and modify code using Repo.archive() to ensure no user-controlled options are passed to it. Implement strict input validation for any options forwarded to archive functions.

Chat Assistant

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

EPSS Chart