CVE-2026-73619

GitPython before 3.1.57 contains an incomplete denylist in its unsafe_git_archive_options guard, which omits the git archive options --add-file and --add-virtual-file. An attacker who can influence the arguments passed to Repo.archive() (for example, in an application or service that exposes archive generation with user-controlled options) can inject these flags, causing git to read arbitrary files from the local filesystem and embed their contents in the returned archive. The result is arbitrary file read with high confidentiality impact, requiring only low privileges and no user interaction. Any deployment of an affected GitPython version in which external input shapes archive options is affected, while applications that never pass attacker-controlled options to Repo.archive() are not meaningfully exposed. A public security advisory exists (GHSA-539m-9xh6-q6rr), but exploitation has not been reported in the wild; EPSS estimates a 0.3% probability of exploitation within 30 days and the flaw is not in CISA KEV.

What to do: Upgrade to GitPython 3.1.57 or later. In the interim, audit code paths that call Repo.archive() and allowlist or strictly validate any user-supplied format/options values, rejecting options that begin with '--'. Operations teams should also review which sensitive local files (e.g., configuration or credential files) an attacker could exfiltrate from affected services.