CVE-2026-87817: GitPython before 3.1.60 Remote Code Execution via Git Directory Impersonation
gitpython-developers · GitPython
Fixed in 3.1.60 · Affected: gitpython-developers before 3.1.60 · Exploitation: unlikely (under 1%)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 36% of scored CVEs
DescriptionCVE.org
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.
Affected products1
From the CVE record. A product or version that is not listed is unknown, not unaffected.
- gitpython-developers · GitPythonbefore 3.1.60
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
- Exploitation
- Unlikely (under 1%). EPSS under 1%, or no score yet.
- CISA KEV
- Not listed
- Public check
- No public nuclei template
- Vendor
- gitpython-developers
- Published
- September 2026
CoverageNo articles yet
No CyberSIXT article names CVE-2026-87817 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.