Directory Traversal Affecting python3.11-gitpython package, versions *


Severity

Recommended
0.0
medium
0
10

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.4% (32nd percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-RHEL10-PYTHON311GITPYTHON-20154804
  • published27 Sept 2026
  • disclosed26 Sept 2026

Introduced: 26 Sep 2026

NewCVE-2026-100689  (opens in a new tab)
CWE-22  (opens in a new tab)

How to fix?

There is no fixed version for RHEL:10 python3.11-gitpython.

NVD Description

Note: Versions mentioned in the description apply only to the upstream python3.11-gitpython package and not the python3.11-gitpython package as distributed by RHEL. See How to fix? for RHEL:10 relevant fixed versions and status.

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.

CVSS Base Scores

version 3.1