CPU exhaustion via quadratic identity-field backtracking
Published Sep 9, 2026 · Updated Sep 9, 2026
Regular expression denial of service in GitPython before 3.1.60 allows attackers to exhaust CPU when an application reads a crafted commit. Actor.name_email_regex applies a backtracking expression to malformed author or committer fields containing an unmatched angle bracket. The attacker must make a crafted commit reachable to a consuming application; accessing the affected field can occupy a CPU for more than two minutes.
Summary
What happened
Regular expression denial of service in GitPython before 3.1.60 allows attackers to exhaust CPU when an application reads a crafted commit. Actor.name_email_regex applies a backtracking expression to malformed author or committer fields containing an unmatched angle bracket. The attacker must make a crafted commit reachable to a consuming application; accessing the affected field can occupy a CPU for more than two minutes.
The record
- CVE
- CVE-2026-87819
- Published
- Sep 9, 2026
- Updated
- Sep 9, 2026
- Vendor
- GitPython Developers
- Product
- GitPython
- Classifications
- T1499
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Sep 9, 2026CVE publishedPublication date reported by the CVE source.
- Sep 9, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <3.1.60
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo