gitpython-developers GitPython up to 3.1.61 Submodule Submodule.update path path traversal

Summaryinfo

A vulnerability was found in gitpython-developers GitPython up to 3.1.61 and classified as problematic. This vulnerability affects the function Submodule.update of the component Submodule. Such manipulation of the argument path leads to path traversal. This vulnerability is documented as CVE-2026-100689. The attack can be executed remotely. There is not any exploit available. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability was found in gitpython-developers GitPython up to 3.1.61 and classified as problematic. Affected by this issue is the function Submodule.update of the component Submodule. The manipulation of the argument path with an unknown input leads to a path traversal vulnerability. Using CWE to declare the problem leads to CWE-22. The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. Impacted is integrity, and availability. CVE summarizes:

GitPython before 3.1.62 does not validate the `path` field read from an untrusted .gitmodules file when updating submodules. While a prior fix (GHSA-hmq2-w58f-27jc) added Submodule._validated_name() to constrain the `name` field, and GitPython's own containment guard Submodule._to_relative_path() is applied in add() and move(), Submodule.update() derives the absolute checkout location from the raw `path` value without that guard. A .gitmodules entry containing directory traversal components (e.g., path = ../../../tmp/escaped) can therefore cause directories to be created via os.makedirs() outside the repository working tree, populated from the submodule URL on the clone path, and removed via shutil.rmtree() when force_remove is used. Exploitation requires an application flow that updates submodules at a non-HEAD commit (such as a historical-commit API); the common clone-then-update flow re-derives the path from a canonical tree lookup and is not affected. The issue is fixed in GitPython 3.1.62.

The advisory is available at github.com. This vulnerability is handled as CVE-2026-100689 since 09/26/2026. The exploitation is known to be easy. The attack may be launched remotely. No form of authentication is required for exploitation. Successful exploitation requires user interaction by the victim. Technical details are known, but there is no available exploit. This vulnerability is assigned to T1006 by the MITRE ATT&CK project.

Upgrading to version 3.1.62 eliminates this vulnerability.

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Type

• Programming Language Software

Vendor

• gitpython-developers

Name

• GitPython

Version

• 3.1.0
• 3.1.1
• 3.1.2
• 3.1.3
• 3.1.4
• 3.1.5
• 3.1.6
• 3.1.7
• 3.1.8
• 3.1.9
• 3.1.10
• 3.1.11
• 3.1.12
• 3.1.13
• 3.1.14
• 3.1.15
• 3.1.16
• 3.1.17
• 3.1.18
• 3.1.19
• 3.1.20
• 3.1.21
• 3.1.22
• 3.1.23
• 3.1.24
• 3.1.25
• 3.1.26
• 3.1.27
• 3.1.28
• 3.1.29
• 3.1.30
• 3.1.31
• 3.1.32
• 3.1.33
• 3.1.34
• 3.1.35
• 3.1.36
• 3.1.37
• 3.1.38
• 3.1.39
• 3.1.40
• 3.1.41
• 3.1.42
• 3.1.43
• 3.1.44
• 3.1.45
• 3.1.46
• 3.1.47
• 3.1.48
• 3.1.49
• 3.1.50
• 3.1.51
• 3.1.52
• 3.1.53
• 3.1.54
• 3.1.55
• 3.1.56
• 3.1.57
• 3.1.58
• 3.1.59
• 3.1.60
• 3.1.61

Website

• Product: https://github.com/gitpython-developers/GitPython/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion