CVE-2026-110860 gitpython-developers CVE debrief

Who should care

Defenders of systems using GitPython 3.1.62 before 3.2.0 should assess exposure and prioritize remediation. Affected operators, platforms, and security teams should review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance. They should also verify affected systems and apply patches according to vendor guidance. Security teams should review compensating controls for exposed systems while remediation is

Why it matters

Defenders should assess exposure of GitPython 3.1.62 before 3.2.0, prioritize remediation, and verify affected systems due to symlink-following flaw.

• Path traversal and potential data corruption
• Index and .gitmodules corruption
• Potential for unauthorized data access

Technical summary

GitPython 3.1.62 before 3.2.0 contains a symlink-following flaw in Submodule.move(), allowing an untrusted repository to corrupt the index and .gitmodules. The vulnerability allows attackers to manipulate the Git repository, potentially leading to data corruption and unauthorized access. The flaw is caused by the Submodule.move() function checking the destination only lexically and not rejecting symbolic links in intermediate path components. This allows an attacker to create a symlink that points outside the worktree, potentially leading to data corruption and unauthorized access.

Defensive priority

Medium priority for GitPython users

Recommended defensive actions

• Assess exposure of GitPython 3.1.62 before 3.2.0
• Prioritize remediation for affected systems
• Verify affected systems and apply patches
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
• Track exceptions, retest remediated assets, and close the item only after evidence is documented

Evidence notes

The CVE record and source item provide details on the symlink-following flaw in GitPython 3.1.62 before 3.2.0. Evidence is limited to public CVE details and may not reflect all affected systems or variations. Defenders should verify affected systems and apply patches according to vendor guidance. The flaw allows an untrusted repository to corrupt the index and .gitmodules, potentially leading to data corruption and unauthorized access. Review compensating controls for exposed systems while remediation is scheduled and verified. Check relevant monitoring, and

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.