# CVE-2026-110860 — gitpython-developers GitPython

> As of 2026-10-14, CVE-2026-110860 is a MEDIUM-severity vulnerability in gitpython-developers GitPython, CVSS v3.1 6.1, EPSS 0.1% (2.2th percentile). No Threadlinqs-tracked threat campaign has been attributed to CVE-2026-110860 as of 2026-10-14; the identifier is re-checked against the Threadlinqs threat corpus on every daily ingest.

**Last updated:** 2026-10-14

## What is CVE-2026-110860?

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.

The record classifies CVE-2026-110860 under weakness class [CWE-59](https://intel.threadlinqs.com/cwe/CWE-59). Its CVSS v3 base vector states that the flaw requires local access to the host, needs no prior authentication, needs a user to take an action first, and has high impact on integrity. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 36 days ago.

## Severity and exploitation probability

- **CVSS v3.1 base score:** 6.1 — MEDIUM (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:L`)
- **CVSS v4.0 base score:** 6.9 (`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`)
- **EPSS (FIRST):** 0.1% probability of exploitation in the next 30 days, higher than 2.2% of all scored CVEs
- **CISA KEV:** Not listed in the CISA Known Exploited Vulnerabilities catalog
- **Threadlinqs priority:** 3.1/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- **Published:** 2026-10-14

## Is CVE-2026-110860 being exploited?

It currently carries a trending score of 30 in the Threadlinqs vulnerability feed.

## Affected products and versions

- [gitpython-developers](https://intel.threadlinqs.com/vendors/gitpython-developers): GitPython

## How to fix CVE-2026-110860

Vendor advisory: [https://github.com/gitpython-developers/GitPython/security/advisories/GHSA-gq48-pqfc-9p58](https://github.com/gitpython-developers/GitPython/security/advisories/GHSA-gq48-pqfc-9p58). Apply the vendor fix referenced above to every affected product listed in this record, then confirm the running version against the vendor advisory.

## Threat activity tracking CVE-2026-110860

No threat campaign in the Threadlinqs corpus currently references CVE-2026-110860, in its CVE list or as an indicator. The linkage is recomputed from the live corpus on every daily ingest, so this section fills in as soon as a tracked campaign cites the identifier.

## Sources

Enriched from CVE.org, NVD, FIRST EPSS, GitHub Security Advisories. This product uses the NVD API but is not endorsed or certified by the NVD.

**Vendor advisory and patch**

- [github.com — vendor advisory](https://github.com/gitpython-developers/GitPython/security/advisories/GHSA-gq48-pqfc-9p58)

**Third-party advisory**

- [vulncheck.com — third party advisory](https://www.vulncheck.com/advisories/gitpython-3.1.62-before-3.2.0-symlink-path-traversal-via-submodule-move)

Canonical: https://intel.threadlinqs.com/cve/CVE-2026-110860
No Threadlinqs detection currently covers CVE-2026-110860; it is re-checked on every ingest.
Indicator values unlock with TL Creds (https://threadlinqs.com/tl-creds); MCP access for AI agents needs Purple: https://intel.threadlinqs.com/mcp
