CVE-2026-73619: GitPython before 3.1.57 Arbitrary File Read via Repo.archive()
GitPython before 3.1.57 contains an incomplete denylist in the unsafegitarchiveoptions 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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/python-gitto a version that resolves this vulnerability.Fixed in 3.1.30-1+deb12u3 - Upgrade
Upgrade
debian/python-gitto a version that resolves this vulnerability.Fixed in 3.1.44-1+deb13u1 - Upgrade
Upgrade
debian/python-gitto a version that resolves this vulnerability.Fixed in 3.1.61-1 - Upgrade
Upgrade
debian/python-gitto a version that resolves this vulnerability.Fixed in 3.1.30-1+deb12u3Fixed in 3.1.44-1+deb13u1Fixed in 3.2.1-1
Event History
Frequently Asked Questions
What is the severity of CVE-2026-73619?
The severity of CVE-2026-73619 is medium, with a score of 6.5.
How do I fix CVE-2026-73619?
To fix CVE-2026-73619, upgrade GitPython to version 3.1.57 or later.
What can an attacker do with CVE-2026-73619?
An attacker can exploit CVE-2026-73619 to read arbitrary files from the filesystem by using the Repo.archive() method.
Which versions of GitPython are affected by CVE-2026-73619?
CVE-2026-73619 affects all versions of GitPython prior to 3.1.57.
What are the implications of CVE-2026-73619?
The implications of CVE-2026-73619 include unauthorized access to sensitive files through the misuse of archive options.