Is CVE-2026-73624 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-73624 being exploited in the wild.

How severe is CVE-2026-73624?

High severity, with a CVSS score of 8.1, published 13 August 2026.

Which products and versions are affected?

gitpython (PyPI) ECOSYSTEM:introduced=0,fixed=3.1.54.

Is there a fix for CVE-2026-73624?

Yes. gitpython (PyPI): upgrade to 3.1.54 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-73624 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-73624?

Check whether you run 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.

CVE-2026-73624: GitPython arbitrary file overwrite in Diffable.diff

CVE-2026-73624 · Severity: high · CVSS 8.1 · Published 2026-08-13

GitPython is a library that developers use to interact with Git repositories programmatically. A vulnerability in the diff method allows attackers to overwrite arbitrary files on the system by injecting malicious git options, potentially compromising critical configuration files or SSH keys. An attacker with low privileges and code execution capability can corrupt or replace any file that the application process has permission to write.

Technologies: gitpython (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2026-73624 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-73624 being exploited in the wild.
How severe is CVE-2026-73624?: High severity, with a CVSS score of 8.1, published 13 August 2026.
Which products and versions are affected?: gitpython (PyPI) ECOSYSTEM:introduced=0,fixed=3.1.54.
Is there a fix for CVE-2026-73624?: Yes. gitpython (PyPI): upgrade to 3.1.54 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-73624 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-73624?: Check whether you run 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.

How to fix

gitpython (PyPI): upgrade to 3.1.54 or later
```
pip install "gitpython>=3.1.54"
```

Technical details

GitPython's Diffable.diff method (used by Commit, Tree, IndexFile, and Submodule classes) fails to validate or sanitize git options passed through kwargs, introducing a command injection vulnerability. The vulnerable code at diff.py:265 inserts the caller-supplied `other` parameter before the `--` separator, allowing it to be parsed as a git option. An attacker can supply `--output=/attacker/chosen/path` either via the `output` kwarg or the `other` parameter to cause git diff-tree to write patch content to an arbitrary file path with process-level privileges. The fix requires adding `check_unsafe_options` guard (as implemented in iter_commits/archive) or placing `--end-of-options` before the other ref. Patched in version 3.1.54.

Affected products

GitPython GitPython before 3.1.54

Identifiers

CVE-2026-73624
GHSA-fjr4-x663-mwxc
PYSEC-2026-3995

Timeline

2026-07-22: disclosed
2026-08-13: advisory
2026: patched: Version 3.1.54 and later

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.