Quick answers
- Is This vulnerability exploited in the wild?
- No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.
- How severe is This vulnerability?
- High severity, with a CVSS score of 8.8, published 9 September 2026.
- Which products and versions are affected?
- GitPython Developers GitPython <= 3.1.59; gitpython (PyPI) <= 3.1.59.
- Is there a fix for This vulnerability?
- A patch was published on 2026-09-09: Version 3.1.60 or later Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is This vulnerability attacked?
- It is attacked over the network, in a software library.
- Am I affected?
- Check whether you run GitPython Developers GitPython or gitpython (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
GitPython fails to properly validate git directory location by testing candidate paths in an unsafe order, checking tracked files (gitdir, commondir, HEAD) before the actual .git directory. This allows attackers to place malicious pre-commit hooks in the repository root that execute when index.commit() is called. The vulnerability affects versions up to 3.1.59 and requires user interaction (calling commit on a cloned or opened repository).
Affected products
- GitPython developers GitPython <= 3.1.59
Timeline
- 2026-08-26: disclosed
- 2026-09-09: advisory
- 2026-09-09: patched: Version 3.1.60 or later