Quick answers
- Is This vulnerability exploited in the wild?
- No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.
- How severe is This vulnerability?
- Medium severity, with a CVSS score of 6.5, published 29 May 2026.
- Which products and versions are affected?
- github.com/go-git/go-git/v5 (Go) <= 5.19.0; github.com/go-git/go-git/v6 (Go) <= 6.0.0-alpha.3; Go-Git <= 5.19.0.
- Is there a fix for This vulnerability?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is This vulnerability attacked?
- It is attacked over the network, in a software library.
- Am I affected?
- Check whether you run github.com/go-git/go-git/v5 (Go), github.com/go-git/go-git/v6 (Go) or Go-Git 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.
Technical details
Multiple denial-of-service (DoS) vulnerabilities exist in go-git due to improper handling of malformed Git object data. The root cause is uncontrolled resource consumption (CWE-400) when parsing malicious .pack, .idx, or loose objects. An attacker can exploit this by providing a crafted repository to an application that uses go-git for operations like cloning, fetching, or opening repositories. This can result in a process panic or resource exhaustion. The issue is fixed in versions 5.19.1 and 6.0.0-alpha.4.
Affected products
- go-git go-git/v5 <= 5.19.0
- go-git go-git/v6 <= 6.0.0-alpha.3
Timeline
- 2026-05-18: disclosed: Initial disclosure to maintainers
- 2026-05-29: advisory: GitHub Advisory published