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 19 August 2026.

Which products and versions are affected?

GitPython developers GitPython <= 3.1.57.

Is there a fix for This vulnerability?

A patch was published on 2026-08-19: GitPython 3.1.58 released with fix 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.

Check whether anything you run is named in the advisory. 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.

GitPython command execution via split_single_char_options guard bypass

Q: Is there a fix for This vulnerability?

A patch was published on 2026-08-19: GitPython 3.1.58 released with fix Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is This vulnerability attacked?

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

Q: Am I affected?

Check whether anything you run is named in the advisory. 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.

Severity: high · CVSS 8.8 · Published 2026-08-19

GitPython is a Python library used to interact with Git repositories. A flaw in GitPython's argument validation allows attackers to bypass safety checks and execute arbitrary system commands on machines running applications that use GitPython. This could allow an attacker to take complete control of the affected system and access or modify sensitive data.

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 19 August 2026.
Which products and versions are affected?: GitPython developers GitPython <= 3.1.57.
Is there a fix for This vulnerability?: A patch was published on 2026-08-19: GitPython 3.1.58 released with fix 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 anything you run is named in the advisory. 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

The vulnerability is an argument injection flaw (CWE-88) in the check_unsafe_options guard used by GitPython's command construction. The guard is designed to prevent dangerous git options like --upload-pack from being passed to git commands. However, by supplying a single-character kwarg combined with split_single_char_options=False, an attacker can cause transform_kwarg to emit a joined token (e.g., -nutouch /tmp/ACE;git-upload-pack) that the guard never validates because _option_candidates only generates the short form ['-n']. The git command parser then interprets this as --upload-pack=<cmd>, achieving arbitrary command execution. The vulnerability affects all guarded methods (clone_from, fetch, pull, push, ls_remote, iter_commits, blame, archive) and requires only that the application forwards user-controlled kwargs to these methods—a pattern already accepted by the library. The fix is available in GitPython 3.1.58.

Affected products

GitPython developers GitPython <= 3.1.57

Timeline

2026-08-04: disclosed
2026-08-19: patched: GitPython 3.1.58 released with fix

References

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