cve.bz

CVE-2026-110860 gitpython-developers gitpython: Link Following

6.9 mediumEPSS 0.2%Fix available

Medium (6.9) in gitpython-developers gitpython. EPSS 0.2% estimated probability of exploitation activity in the next 30 days. Fixed in gitpython 3.2.0.

On this page
GitPython from 3.1.62 before 3.2.0 contains a symlink-following flaw in Submodule.move(), which checks the destination only lexically and does not reject symbolic links in intermediate path components. An untrusted repository can commit a symlink such as vendor pointing outside the worktree, so an application moving an initialized submodule beneath it relocates the checkout externally and corrupts the index and .gitmodules.

Severity

CVSS 4.0

6.9 medium
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:N/VI:H/VA:L/SC:N/SI:N/SA:N

CVSS 3.1

6.1 medium
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:L
EPSS
0.2% (unchanged from 0.2% a week ago; 0.1% 30 days ago) estimated probability of exploitation activity in the next 30 days; 8th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: partial, assessed 2026-10-26. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-59 Improper Link Resolution Before File Access (Link Following)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-110860 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-110860?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-110860?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-110860 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
gitpython-developers GitPythonfrom 3.1.62 before 3.2.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-gq48-pqfc-9p58PyPIgitpython<3.2.03.2.0

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12python-git3.1.30-1+deb12u3DEBIAN-CVE-2026-110860
Debian13python-git3.1.44-1+deb13u1DEBIAN-CVE-2026-110860
Debian14python-git3.2.1-1DEBIAN-CVE-2026-110860
Ubuntu26.10, Pro:14.04:LTS, Pro:16.04:LTS and 5 morepython-gitno fix listedUBUNTU-CVE-2026-110860

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu.

Red Hat

Red Hat rates this Moderate.

Red Hat's 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.

Red Hat's 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.

ProductPackageStateAdvisory
Exploit Intelligenceexploit-intelligence/vulnerability-analysis-rhel9Out of support scope
Red Hat AI Inference Serverrhaiis/vllm-cpu-rhel9Fix deferred
Red Hat AI Inference Serverrhaiis/vllm-tpu-rhel9Fix deferred
Red Hat Ansible Automation Platform 2ansible-automation-platform-24/controller-rhel8Out of support scope
Red Hat Ansible Automation Platform 2ansible-automation-platform-25/controller-rhel8Out of support scope
Red Hat Ansible Automation Platform 2ansible-automation-platform-26/controller-rhel9Fix deferred
Red Hat Ansible Automation Platform 2ansible-automation-platform-26/hub-rhel9Fix deferred
Red Hat Ansible Automation Platform 2ansible-automation-platform-27/controller-rhel9Fix deferred
Red Hat Ansible Automation Platform 2ansible-automation-platform-27/hub-rhel9Fix deferred
Red Hat Ansible Automation Platform 2automation-controllerFix deferred
Red Hat Ansible Automation Platform 2python3.11-gitpythonFix deferred
Red Hat Ansible Automation Platform 2python3.12-gitpythonFix deferred
Red Hat Ansible Automation Platform 2python3x-gitpythonOut of support scope
Red Hat Ansible Automation Platform 2python-gitpythonOut of support scope
Red Hat Enterprise Linux AI (RHEL AI) 3rhelai3/bootc-cuda-rhel9Fix deferred
Red Hat Enterprise Linux AI (RHEL AI) 3rhelai3/bootc-gaudi-rhel9Fix deferred
Red Hat Enterprise Linux AI (RHEL AI) 3rhelai3/bootc-rocm-rhel9Fix deferred
Red Hat Enterprise Linux AI (RHEL AI) 3rhelai3/disk-image-cuda-rhel9Fix deferred
Red Hat OpenShift AI (RHOAI)rhoai/odh-feature-server-rhel9Fix deferred
Red Hat OpenShift AI (RHOAI)rhoai/odh-mlflow-rhel9Fix deferred
34 more in the JSON and on Red Hat's page.

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-110860.

Attack patterns (CAPEC)

  • CAPEC-17 Using Malicious Files Likelihood: High · Severity: Very High
  • CAPEC-35 Leverage Executable Code in Non-Executable Files Likelihood: High · Severity: Very High
  • CAPEC-76 Manipulating Web Input to File System Calls Likelihood: High · Severity: Very High
  • CAPEC-132 Symlink Attack Likelihood: Low · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON