GitPython versions before 3.1.54 contain a remote code execution vulnerability in the check_unsafe_options guard. By smuggling git options into single‑character keyword arguments, an attacker can supply crafted option dictionaries to methods such as clone_from, fetch, pull, push, ls_remote, iter_commits, blame, or archive. This bypass allows the attacker to exercise the --upload-pack parameter and execute arbitrary OS commands, exposing confidentiality and integrity of the system.

The vulnerability affects the GitPython library maintained by the GitPython developers. Any Python project that depends on a pre‑3.1.54 release of GitPython is at risk. The impact depends on the privileges of the process executing the library, as the vulnerability allows remote execution of OS commands through the library's API. No specific operating system or environment is enumerated, so the scope is determined by how the library is used in the application.

The CVSS score of 8.7 classifies this flaw as high severity. EPSS data is not available, so current exploitation likelihood is unknown. The flaw is not listed in the CISA KEV catalog. Based on the description, the likely attack vector involves an attacker who can control the arguments passed to GitPython functions in a running application. If the application runs with elevated privileges, the attacker could achieve full system compromise. Although the EPSS score is not disclosed, the nature of the flaw—arbitrary shell command execution—makes it a highly valuable target for malicious actors.