# CVE-2026-87819: GitPython before 3.1.60 Denial of Service via ReDoS

> Attackers can cause denial of service in GitPython by crafting malicious commit objects that trigger excessive CPU usage via regex backtracking.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 Sep 2026
- **Updated:** 8 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-87819, ECHO-5764-2a31-d004, GHSA-g5vv-9gxw-82hx, MGASA-2026-0450, MINI-39hm-j9xq-v3xw, MINI-gxp9-rcv9-464v, MINI-qjwg-c74m-6hm8, MINI-rm6p-qjhp-6gfg, PYSEC-2026-3984, UBUNTU-CVE-2026-87819

## What is CVE-2026-87819?

CVE-2026-87819 is a high-severity denial of service vulnerability in gitpython-developers GitPython, published on 9 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

GitPython before 3.1.60 contains a regular expression denial of service vulnerability in Actor.name_email_regex that processes commit author and committer fields. Attackers can craft a commit object with a malformed author field containing an unterminated angle bracket to cause quadratic backtracking, exhausting CPU resources for over two minutes per commit access.

Weakness: CWE-1333 (Inefficient Regular Expression Complexity)

## Which versions are affected by CVE-2026-87819?

3 open source packages ship an affected version, including gitpython and GitPython. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `gitpython` | PyPI | All versions | 3.1.60 |
| `gitpython` | PyPI | All versions | 3.1.60 |
| `GitPython` | PyPI | All versions | 3.1.60 |

Products: Gitpython Project Gitpython.

## How do I fix CVE-2026-87819?

Upgrade gitpython to 3.1.60 or later.

## Is CVE-2026-87819 being exploited?

There is no known exploitation of CVE-2026-87819 in the wild and no public exploit code.

## Other vulnerabilities in gitpython-developers GitPython

- [CVE-2023-40267](https://insights.sbomify.com/CVE-2023-40267/): GitPython vulnerable to remote code execution due to insufficient sanitization of input arguments (critical 9.8)
- [CVE-2026-78676](https://insights.sbomify.com/CVE-2026-78676/): GitPython before 3.1.59 Remote Code Execution via Config Injection (critical 9.3)
- [CVE-2026-67324](https://insights.sbomify.com/CVE-2026-67324/): GitPython 3.1.50 Authentication Bypass via Joined Short Options (critical 9.3)
- [CVE-2026-42215](https://insights.sbomify.com/CVE-2026-42215/): GitPython: Command injection via Git options bypass (high 8.8)
- [CVE-2026-87817](https://insights.sbomify.com/CVE-2026-87817/): GitPython before 3.1.60 Remote Code Execution via Git Directory Impersonation (high 8.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-87819 and fix it if it is affected.

What it is: CVE-2026-87819 is a high-severity denial of service vulnerability in gitpython-developers GitPython, published on 9 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-87819 in the wild and no public exploit code.

Affected packages and fixed versions:
- gitpython (PyPI): affected all versions; fixed in 3.1.60
- gitpython (PyPI): affected all versions; fixed in 3.1.60
- GitPython (PyPI): affected all versions; fixed in 3.1.60

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-87819/ (Markdown: https://insights.sbomify.com/CVE-2026-87819/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-87819
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-87819
- OSV: https://osv.dev/vulnerability/CVE-2026-87819

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-87819/
Summaries are generated and may contain mistakes; the official description above is the record.