Secuno
ENNL
Book demo

CVE-2026-87819

7.5 HIGHPublic exploitEPSS 0.28%
  1. Published9 Sept 2026

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.

CVSS 3.1 breakdown

Attack vectorNetwork
Attack complexityLow
Privileges requiredNone
User interactionNone
ScopeUnchanged
ConfidentialityNone
IntegrityNone
AvailabilityHigh
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected products

Gitpython Project Gitpython< 3.1.60

Remediation

Fixed in
Gitpython Project Gitpython≥ 3.1.60

References

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

CVE-2026-826179.8
The two built-in name-finder patterns exposed by…
CVE-2026-527789.8
YesWiki is a wiki system written in PHP. Prior to version 4.6.6, an unsafe execution…
CVE-2026-354589.8
Gotenberg is an API for converting document formats. In 8.29.1 and earlier, Gotenberg…
CVE-2025-624848.1
Inefficient regular expression complexity in certain Zoom Workplace Clients before…

Frequently asked

Is CVE-2026-87819 being actively exploited?

CVE-2026-87819 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 0.28%.

How severe is CVE-2026-87819?

CVE-2026-87819 has a CVSS 3.1 base score of 7.5, rated high. EPSS estimates a 0.28% probability of exploitation.

Which products are affected by CVE-2026-87819?

Affected products include Gitpython Project Gitpython.

How do I fix CVE-2026-87819?

Upgrade affected software to a fixed version, for example Gitpython Project Gitpython 3.1.60 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2026-87819 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation worksBook a demo

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.