CVE-20XX-?

Gitpython Project Gitpython CVEs.

Published CVEs affecting Gitpython Project Gitpython, ranked by exploit odds.

6 CVEs · updated 2026-11-06 06:52 UTC

Reset all
  1. CVE-2026-78677

    GitPython before 3.1.59 omits --separate-git-dir from unsafe_git_clone_options, allowing attackers to create arbitrary git directories outside the intended clone destination. Attackers can pass a separate_git_dir parameter to Repo.clone_from() or Repo.clone() to redirect repository metadata to an attacker-controlled filesystem path, enabling arbitrary directory creation and potential hook execution.

    Disclosure Gitpython Project Gitpython

    8.7 HIGH 0.7% exploit odds Fix listed
  2. CVE-2026-73620

    GitPython before 3.1.57 fails to guard git option forwarding in IndexFile.checkout() and TagReference.create(), allowing attackers to pass unsafe options via kwargs. Attackers can use --prefix to overwrite arbitrary files with repository content or -F to read arbitrary files returned in-band.

    Disclosure Gitpython Project Gitpython

    7.2 HIGH 0.6% exploit odds Fix listed
  3. CVE-2026-73622

    GitPython before 3.1.55 fails to disable environment variable expansion in Remote.create() and Submodule.add() URL handling, allowing attackers to exfiltrate secrets by supplying URLs containing variable references. Attackers can craft URLs with environment variable tokens that are expanded into .git/config and .gitmodules, then transmitted to attacker-controlled hosts during fetch or pull operations.

    Disclosure Gitpython Project Gitpython

    8.7 HIGH 0.5% exploit odds Fix listed
  4. CVE-2026-76222

    GitPython before 3.1.58 fails to validate submodule names from .gitmodules files, allowing attackers to create Git repositories at arbitrary filesystem paths outside the intended clone directory. Attackers can craft malicious repositories with traversal sequences in submodule names that GitPython processes during submodule initialization, creating attacker-controlled Git repositories at escaped filesystem locations.

    Disclosure Gitpython Project Gitpython

    8.4 HIGH 0.4% exploit odds Fix listed
  5. CVE-2026-44243

    GitPython is a python library used to interact with Git repositories. Prior to version 3.1.48, a vulnerability in GitPython allows attackers who can supply a crafted reference path to an application using GitPython to write, overwrite, move, or delete files outside the repository’s .git directory via insufficient validation of reference paths in reference creation, rename, and delete operations. This issue has been patched in version 3.1.48.

    Disclosure Library Gitpython Project Gitpython

    7.8 HIGH 0.4% exploit odds Fix listed
  6. CVE-2026-67322

    GitPython before 3.1.52 is vulnerable to environment-variable exfiltration in Repo.clone_from(). The caller-supplied remote URL is passed through Git.polish_url(), which on non-Cygwin platforms calls os.path.expandvars() on the URL before invoking git clone. An attacker who controls the clone URL can embed $NAME or ${NAME} tokens that are expanded to the values of the hosting process's environment variables (e.g., AWS_SECRET_ACCESS_KEY or GITHUB_TOKEN). The resulting URL, now containing the secret, is transmitted over the network to an attacker-controlled host during the clone attempt, disclosing the secret.

    Disclosure Gitpython Project Gitpython

    8.7 HIGH 0.3% exploit odds Fix listed

All CVEs affecting Gitpython Project Gitpython that appear in CVE.org and NVD, sorted by how likely they are to be exploited (EPSS), with fix status and timeline.