CVE-2026-73619 GitPython before 3.1.57 Arbitrary File Read via Repo.archive()

High 7.1 Published Updated

Attackers can read arbitrary files from the filesystem by exploiting an incomplete denylist in GitPython's Repo.archive() method.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

What is CVE-2026-73619?

CVE-2026-73619 is a high-severity path traversal vulnerability in gitpython-developers GitPython, published on 13 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

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

Weakness: CWE-73

Which versions are affected by CVE-2026-73619?

3 open source packages ship an affected version, including gitpython and GitPython. It affects 1 product.

PackageAffectedFixed in
gitpython PyPIAll versions3.1.57
gitpython PyPIAll versions3.1.57
GitPython PyPIAll versions3.1.57

Products include Gitpython Project Gitpython.

How do I fix CVE-2026-73619?

Upgrade gitpython to 3.1.57 or later.

Upgrade, and resolve every user-supplied path against an allowed base folder before opening it. More about Path traversal.

Is CVE-2026-73619 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-73619 exists.

Sources

Also known as CLSA-2026-1787036379, DEBIAN-CVE-2026-73619, ECHO-5a03-fb3b-9930, ECHO-c457-5e3c-26ac, GHSA-539m-9xh6-q6rr, GHSA-m3x4-5jfw-2mqc and 8 more.

Is CVE-2026-73619 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free