GitPython versions prior to 3.1.58 do not validate submodule names in .gitmodules files. A malicious repository can include traversal sequences in a submodule name, causing GitPython to create a repository at an arbitrary path outside the intended clone directory during submodule initialization. This results in unauthorized file creation or modification, which can be leveraged for code execution or persistence.

The vulnerability affects the GitPython library developed by the GitPython developers. All releases before 3.1.58 are impacted. Users integrating GitPython into applications that clone or initialize submodules are exposed.

The CVSS score of 8.4 indicates a high severity impact. EPSS is not available, and the issue is not listed in CISA KEV, suggesting limited public exploitation data. Attackers can exploit this by delivering a crafted .gitmodules file when the application processes a repository; the attack vector is inferred to be remote when the library is used in a service exposed to untrusted input.