GHSA-HMQ2-W58F-27JC

GitPython: Arbitrary Git Repository Creation Outside the Working Tree via Unvalidated .gitmodules Submodule Name in GitPython

Path traversal (CWE-22) / external control of file path (CWE-73) leading to arbitrary directory and Git-repository creation outside the intended clone directory. Integrity impact is High (attacker chooses destination path and, via the submodule URL, much of the written content); Confidentiality impact is None (only creation was demonstrated); Availability impact is Low-Medium (disk-exhaustion potential). No authentication is required; the attacker only needs to control a repository the victim clones and initializes submodules for - a routine, often fully-automatic operation in CI pipelines, IDE integrations, and dependency-management tooling.

Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files. Typical impact: unauthorized file read or write outside the intended directory.

GHSA-HMQ2-W58F-27JC has a CVSS score of 8.2 (High). The vector is network-reachable, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (3.1.58); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

1. What is GHSA-HMQ2-W58F-27JC? GHSA-HMQ2-W58F-27JC is a high-severity path traversal vulnerability in GitPython (pip), affecting versions <= 3.1.57. It is fixed in 3.1.58. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.
2. How severe is GHSA-HMQ2-W58F-27JC? GHSA-HMQ2-W58F-27JC has a CVSS score of 8.2 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of GitPython are affected by GHSA-HMQ2-W58F-27JC? GitPython (pip) versions <= 3.1.57 is affected.
4. Is there a fix for GHSA-HMQ2-W58F-27JC? Yes. GHSA-HMQ2-W58F-27JC is fixed in 3.1.58. Upgrade to this version or later.
5. Is GHSA-HMQ2-W58F-27JC exploitable, and should I be worried? Whether GHSA-HMQ2-W58F-27JC is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether GHSA-HMQ2-W58F-27JC is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix GHSA-HMQ2-W58F-27JC? Upgrade GitPython to 3.1.58 or later.

Other vulnerabilities in GitPython