8.8High
Gitpython Project Gitpython
CVE-2026-87817
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.
What this means for your business
- It affects Gitpython Project Gitpython. It matters if your company, or a supplier that handles your data, runs it.
- Code showing how to exploit it has been published, but real attacks have not been confirmed.
- An attacker can use it remotely, over a network, without a login, but only after tricking someone into an action such as opening a file or a link.
- FIRST's prediction model gives it a 0.3% chance of attack attempts being seen in the next 30 days, ranking above 23% of all known flaws.
What to do
- 1Check whether your company or your suppliers run Gitpython Project Gitpython, and which version. The affected versions are listed further down this page.
- 2If you do, apply the vendor's fix. A patch or vendor advisory has been published.
Not sure if your company is exposed?
Fastnexa’s certified penetration testers can check whether attackers could use this flaw, or others like it, against your websites, apps and network. The full test is free for our first 10 founding clients until 31 December 2026.
Scoring
- CVSS
- 8.8 (v3.1)
- Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H- CVSS v4
- 8.7
- Weakness
- CWE-94
- Assigned by
- disclosure@vulncheck.com
Dates
- Published
- 2026-09-09
- Last modified
- 2026-09-16
- Sources
- NVD
Affected products
- Gitpython Project Gitpython- 3.1.60
As listed in the NVD configuration data. Not a statement about your estate.