CVE-2026-110860

Awaiting Analysis Awaiting Analysis - Queue

Symlink Following Vulnerability in GitPython

Publication date: 2026-10-14

Last updated on: 2026-10-14

Assigner: VulnCheck

Description

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-10-14

Last Modified

2026-10-14

Generated

2026-10-19

AI Q&A

2026-10-15

EPSS Evaluated

2026-10-18

NVD

CVE-2026-110860

EUVD

EUVD-2026-101743

Affected Vendors & Products

Vendor	Product	Version / Range
gitpython-developers	GitPython	3.1.62

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-59	The product attempts to access a file based on the filename, but it does not properly prevent that filename from identifying a link or shortcut that resolves to an unintended resource.

Attack-Flow Graph

Executive Summary

GitPython versions from 3.1.62 before 3.2.0 have a symlink-following flaw in the Submodule.move() function. The function checks the destination path only lexically and does not reject symbolic links in intermediate path components. This allows an attacker to commit a symlink in a repository, such as one named 'vendor' pointing outside the worktree. When an application moves an initialized submodule beneath this symlink, it relocates the checkout externally, corrupting the index and .gitmodules files.

Detection Guidance

To detect this vulnerability, inspect GitPython versions in use. Check for symlinks in submodule paths or unexpected file modifications. Commands like 'pip show GitPython' or 'git submodule status' may help identify affected repositories.

Impact Analysis

This vulnerability can lead to repository corruption by allowing an attacker to overwrite files outside the intended worktree. It may cause data loss or unintended changes to the Git repository structure. Developers using vulnerable GitPython versions risk compromising their local or shared repositories if they interact with untrusted repositories.

Compliance Impact

This vulnerability does not directly affect compliance with GDPR or HIPAA as it involves a symlink-following flaw in GitPython's Submodule.move() function, which could corrupt repository state but does not inherently expose or leak sensitive data.

Mitigation Strategies

Upgrade GitPython to version 3.2.0 or later. Avoid using untrusted repositories. Review submodule configurations for suspicious symlinks. Temporarily disable submodule operations if necessary.

Hi! I’m here to help you understand CVE-2026-110860. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70