CVE-2025-21614 — go-git.v4
HIGHCVE-2025-21614 is a high-severity (CVSS 7.5) Uncontrolled Resource Consumption vulnerability in gopkg.in/src-d/go-git.v4. A fix is available for gopkg.in/src-d/go-git.v4 — see the affected versions and patch details below.
go-git clients vulnerable to DoS via maliciously crafted Git server replies
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2025-21614.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2025-21614 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,238 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
gopkg.in/src-d/go-git.v4🐹github.com/go-git/go-git/v5🐹github.com/go-git/go-gitReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
go-git is a highly extensible git implementation library written in pure Go. A denial of service (DoS) vulnerability was discovered in go-git versions prior to v5.13. This vulnerability allows an attacker to perform denial of service attacks by providing specially crafted responses from a Git server which triggers resource exhaustion in go-git clients. Users running versions of go-git from v4 and above are recommended to upgrade to v5.13 in order to mitigate this vulnerability.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | gopkg.in/src-d/go-git.v4 | ≥ 4.0.0 | No fix |
| 🐹Go | github.com/go-git/go-git/v5 | all versions | 5.13.0go get github.com/go-git/go-git/v5@v5.13.0 |
| 🐹Go | github.com/go-git/go-git | ≥ 4.0.0 | No fix |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for gopkg.in/src-d/go-git.v4, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
No patched version of gopkg.in/src-d/go-git.v4 has shipped for CVE-2025-21614 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2025-21614 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2025-21614. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat Advanced Cluster Security 4.4 | advanced-cluster-security/rhacs-main-rhel8:4.4.8-2 | RHSA-2025:1468 |
| Red Hat Advanced Cluster Security 4.5 | advanced-cluster-security/rhacs-main-rhel8:4.5.6-2 | RHSA-2025:1334 |
| Red Hat Advanced Cluster Security 4.6 | advanced-cluster-security/rhacs-central-db-rhel8:4.6.2-2 | RHSA-2025:0907 |
| Red Hat Enterprise Linux 8 | grafana-0:9.2.10-21.el8_10 | RHSA-2025:0401 |
| Red Hat Enterprise Linux 9.4 Extended Update Support | grafana-0:9.2.10-21.el9_4 | RHSA-2025:0662 |
| Red Hat OpenShift Container Platform 4.16 | openshift4/ose-helm-rhel9-operator:v4.16.0-202502130836.p0.g26e182e.assembly.stream.el9 | RHSA-2025:1704 |
| Red Hat OpenShift Container Platform 4.17 | openshift4/oc-mirror-plugin-rhel9:v4.17.0-202501221434.p0.g39bedc7.assembly.stream.el9 | RHSA-2025:0654 |
| Red Hat OpenShift Container Platform 4.17 | openshift4/ose-helm-rhel9-operator:v4.17.0-202502051104.p0.g61a705e.assembly.stream.el9 | RHSA-2025:1119 |
Frequently Asked Questions
Is CVE-2025-21614 in your dependencies?
O3 Security finds CVE-2025-21614 across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.