Is CVE-2026-110856 exploited in the wild?

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

How severe is CVE-2026-110856?

High severity, with a CVSS score of 7.5, published 14 October 2026.

Which products and versions are affected?

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

How is CVE-2026-110856 attacked?

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

Am I affected by CVE-2026-110856?

Check whether you run GitPython Developers 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-110856: GitPython regular expression denial of service in parse_actor_and_date

CVE-2026-110856 · Severity: high · CVSS 7.5 · Published 2026-10-14

GitPython is a widely-used library that reads and processes Git repository data, including commit and tag metadata. A flaw in how it parses author, committer, and tagger fields allows an attacker to serve a malicious repository that causes severe CPU exhaustion when the library attempts to read commits or tags. An organization processing untrusted repositories—such as CI/CD systems or code scanners—could experience service degradation or outages.

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

Quick answers

Is CVE-2026-110856 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-110856 being exploited in the wild.
How severe is CVE-2026-110856?: High severity, with a CVSS score of 7.5, published 14 October 2026.
Which products and versions are affected?: GitPython Developers GitPython before 3.2.0; gitpython (PyPI) ECOSYSTEM:introduced=0,fixed=3.2.0.
Is there a fix for CVE-2026-110856?: Yes. gitpython (PyPI): upgrade to 3.2.0 or later. Until then: Restrict GitPython's use to repositories from trusted sources, or disable automatic fetch operations from untrusted remotes until the library can be upgraded. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-110856 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-110856?: Check whether you run GitPython Developers 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"
```

Restrict GitPython's use to repositories from trusted sources, or disable automatic fetch operations from untrusted remotes until the library can be upgraded.

Technical details

The _re_actor_epoch regular expression pattern in parse_actor_and_date uses a backtracking-prone pattern (.+?) that, combined with a following (.*) group, can match the same input in multiple ways when the required trailing epoch and timezone fields are missing or malformed. On a 32 KB line of spaces, this causes quadratic backtracking that takes ~7 seconds per access on GitPython 3.1.62. An attacker can embed such objects in a repository and serve them via git fetch; the objects bypass default fsck checks.

Affected products

GitPython developers GitPython before 3.2.0

Identifiers

CVE-2026-110856
GHSA-m64x-33q8-m5h7

Timeline

2026-10-14: disclosed

References

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