CVE-2026-110855 gitpython-developers CVE debrief

Who should care

Defenders responsible for GitPython deployments, especially those interacting with untrusted repositories, should assess exposure and prioritize verification and remediation. This includes operators managing affected systems, platform administrators, vulnerability management teams, and security teams responsible for monitoring and incident response.

Why it matters

Defenders should prioritize verifying and upgrading to GitPython 3.2.0 or later, especially in environments where GitPython is used to interact with untrusted repositories, as the information disclosure vulnerability can lead to potential exposure of secrets.

• Potential exposure of secrets in .git/modules directory names and DEBUG logs
• Verification of GitPython version and repository access controls required
• Monitoring of DEBUG logs for potential exposure of secrets necessary

Technical summary

GitPython before 3.2.0 contains an information disclosure vulnerability that allows malicious repositories to expand environment variables via separate_git_dir in Repo._clone(), which omits expand_vars=False when calling Git.polish_url(). Attackers can craft a .gitmodules submodule name containing variable syntax so that clone plus submodule_update exposes secrets in .git/modules directory names and DEBUG logs. The vulnerability is addressed in GitPython 3.2.0 or later, emphasizing the need for defenders to verify and upgrade their deployments.

Defensive priority

Defenders should prioritize verifying and upgrading to GitPython 3.2.0 or later, especially in environments where GitPython is used to interact with untrusted repositories.

Recommended defensive actions

• Verify GitPython version and upgrade to 3.2.0 or later
• Review and restrict access to untrusted repositories
• Monitor DEBUG logs for potential exposure of secrets
• Perform vulnerability assessment for affected GitPython deployments
• Implement compensating controls for exposed systems
• Track exceptions and retest remediated assets
• Review relevant monitoring, detection, and logs for exposed assets

Evidence notes

The CVE record and source item provide details on the information disclosure vulnerability in GitPython before 3.2.0, which allows malicious repositories to expand environment variables via separate_git_dir in Repo._clone().

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.