GitPython versions from 2.9.2 up to but not including 4.1.0 contain a vulnerability where an attacker-controlled submodule name in a cloned repository's .gitmodules file can cause GitPython to create and initialize a Git repository outside the intended working directory. This occurs because GitPython does not validate submodule names for path traversal sequences, allowing arbitrary filesystem paths for submodule Git directories. The vulnerability requires a victim to clone a malicious repository and run submodule initialization via GitPython. The issue is fixed in GitPython 4.1.0.