CVE-2026-110860

Description

A flaw was found in GitPython. This vulnerability allows an attacker to write files outside the intended working directory and corrupt repository metadata by tricking an application into processing a crafted repository containing symbolic links. Because the Submodule.move() function validates destination paths only lexically without resolving intermediate symbolic links, moving an initialized submodule can cause GitPython to follow links pointing outside the working tree and relocate submodule checkouts to an arbitrary location.

Statement

Red Hat Product Security rates this GitPython flaw as Moderate. The Submodule.move() function of GitPython validates its destination path only lexically and does not resolve symbolic links in intermediate path components. An attacker can commit a symbolic link pointing outside the working tree into an untrusted repository; when an application that has cloned or opened such a repository moves an initialized submodule beneath that symlink, GitPython follows the link and relocates the submodule checkout to an attacker-influenced location outside the working tree, writing files outside the intended directory and corrupting repository metadata such as the index and .gitmodules. Exploitation requires local processing of a crafted repository with user interaction and no prior privileges; the impact is limited to high integrity impact and low availability impact within the privileges of the process running GitPython, with no direct confidentiality impact (CVSS 6.1, AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:L), consistent with the upstream CVSS 3.1 severity. GitPython is shipped in multiple Red Hat offerings, including Red Hat OpenStack Platform, Red Hat Ansible Automation Platform, Red Hat Enterprise Linux AI, and Red Hat Insights. The currently recorded affected components are either in streams that fall outside Red Hat's full support scope (resolved as out of support scope) or deferred, because Red Hat does not file trackers for Moderate-severity flaws whose CVSS score is below 7.0. For the deferred components the fix is postponed to a future release; the residual risk is that an application processing an attacker-controlled repository could relocate files outside the intended working directory.

Mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability. Upgrading GitPython to version 3.2.0 or later, which upstream lists as unaffected for this issue, resolves the flaw where such an update is available in the affected offering.

Common Vulnerability Scoring System (CVSS) Score Details

Info alert:Important note

CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).

The following CVSS metrics and score provided are preliminary and subject to review.

CVSS v3 Score Breakdown

Red HatNVDcve.org
Base Score6.1N/A6.1
Attack VectorLocalN/ALocal
Attack ComplexityLowN/ALow
Privileges RequiredNoneN/ANone
User InteractionRequiredN/ARequired
ScopeUnchangedN/AUnchanged
ConfidentialityNoneN/ANone
Integrity ImpactHighN/AHigh
Availability ImpactLowN/ALow

Vector

Red Hat: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:L

cve.org: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:L

Understanding the Weakness (CWE)

Confidentiality,Integrity,Access Control

Technical Impact: Read Files or Directories; Modify Files or Directories; Bypass Protection Mechanism

An attacker may be able to traverse the file system to unintended locations and read or overwrite the contents of unexpected files. If the files are used for a security mechanism then an attacker may be able to bypass the mechanism.

Other

Technical Impact: Execute Unauthorized Code or Commands

Windows simple shortcuts, sometimes referred to as soft links, can be exploited remotely since a ".LNK" file can be uploaded like a normal file. This can enable remote execution.

Frequently Asked Questions

Want to get errata notifications? Sign up here.