CVE-2026-87817 GitPython before 3.1.60 Remote Code Execution via Git Directory Impersonation

High 8.7 Published Updated

Attackers can execute arbitrary code by impersonating the git directory and placing malicious hooks, affecting users of the GitPython library.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
A user has to click or open something
Fix
Available

What is CVE-2026-87817?

CVE-2026-87817 is a high-severity code injection vulnerability in gitpython-developers GitPython, published on 9 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

Official description

GitPython before 3.1.60 fails to properly validate the git directory location, allowing attackers to impersonate the git directory using tracked files like gitdir, commondir, and HEAD. Attackers can execute arbitrary code by placing a malicious pre-commit hook in the tracked hooks directory that executes when a victim calls index.commit() on a cloned or opened repository.

Weakness: CWE-94

Which versions are affected by CVE-2026-87817?

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

PackageAffectedFixed in
gitpython PyPIAll versions3.1.60
gitpython PyPIAll versions3.1.60
gitpython PyPIAll versions3.1.60

Products include Gitpython Project Gitpython.

How do I fix CVE-2026-87817?

Upgrade gitpython to 3.1.60 or later.

Upgrade, and never evaluate templates, expressions or code built from user input. More about Code injection.

Is CVE-2026-87817 being exploited?

There is no known exploitation of CVE-2026-87817 in the wild and no public exploit code.

Sources

Also known as DEBIAN-CVE-2026-87817, ECHO-da18-07c8-f77a, GHSA-239g-whfq-7xj9, MINI-36cp-prvh-9228, MINI-78gr-h522-rmv9, MINI-fvj2-g7hw-46q6 and 3 more.

Is CVE-2026-87817 in your software?

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

Check your SBOMs for free