Is CVE-2026-110855 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-110855 being exploited in the wild.

How severe is CVE-2026-110855?

Medium severity, with a CVSS score of 6.5, published 14 October 2026.

Which products and versions are affected?

GitPython before 3.2.0; gitpython (PyPI) ECOSYSTEM:introduced=0,fixed=3.2.0.

Is there a fix for CVE-2026-110855?

Yes. gitpython (PyPI): upgrade to 3.2.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-110855 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-110855?

Check whether you run GitPython or gitpython (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-110855: GitPython environment variable expansion in submodule handling

CVE-2026-110855 · Severity: medium · CVSS 6.5 · Published 2026-10-14

GitPython, a library for working with Git repositories, exposes environment variables through a flaw in how it processes malicious repository configuration. An attacker can craft a specially named submodule in a Git repository that, when cloned and updated, causes GitPython to expand environment variables (such as AWS credentials or API keys) and expose their values in both on-disk directory names and debug logs. This allows attackers to steal sensitive secrets from CI/CD pipelines and other automated systems.

Technologies: GitPython, gitpython (PyPI). Vendors: GitPython, PyPI.

Quick answers

Is CVE-2026-110855 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-110855 being exploited in the wild.
How severe is CVE-2026-110855?: Medium severity, with a CVSS score of 6.5, published 14 October 2026.
Which products and versions are affected?: GitPython before 3.2.0; gitpython (PyPI) ECOSYSTEM:introduced=0,fixed=3.2.0.
Is there a fix for CVE-2026-110855?: Yes. gitpython (PyPI): upgrade to 3.2.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-110855 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-110855?: Check whether you run GitPython or gitpython (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

gitpython (PyPI): upgrade to 3.2.0 or later
```
pip install "gitpython>=3.2.0"
```

Technical details

The vulnerability exists in Repo._clone() which calls Git.polish_url() on the separate_git_dir parameter without passing expand_vars=False, unlike other code paths handling untrusted data. A malicious .gitmodules submodule name containing environment variable syntax (e.g., $AWS_SECRET_KEY) is passed to Git.polish_url(), which expands the variables via os.path.expandvars(). The expanded secret then appears in .git/modules directory names (persistent on disk) and in DEBUG-level Popen logs that are not redacted like credential-bearing URL arguments. Exploitation requires only a standard clone + submodule_update workflow on the attacker's repository.

Affected products

GitPython GitPython before 3.2.0

Identifiers

CVE-2026-110855
GHSA-fx3j-rwgx-fr94

Timeline

2026-09-30: disclosed
2026-10-14: advisory

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.