CVE-2025-21613 — go-git.v4
CVE-2025-21613 is a CWE-88 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 has an Argument Injection via the URL field
Exploitation Status
No confirmed exploitation observed yet
- A successful exploit gives an attacker total control of the affected component, not partial access.
- 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-21613.
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.
Real-World Exposure
gopkg.in/src-d/go-git.v4🐹github.com/go-git/go-git/v5Real-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
Impact
An argument injection vulnerability was discovered in go-git versions prior to v5.13.
Successful exploitation of this vulnerability could allow an attacker to set arbitrary values to git-upload-pack flags. This only happens when the file transport protocol is being used, as that is the only protocol that shells out to git binaries.
Affected versions
Users running versions of go-git from v4 and above are recommended to upgrade to v5.13 in order to mitigate this vulnerability.
Workarounds
In cases where a bump to the latest version of go-git is not possible, we recommend users to enforce restrict validation rules for values passed in the URL field.
Credit
Thanks to @vin01 for responsibly disclosing this vulnerability to us.
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 |
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-21613 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-21613 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2025-21613. 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.
This vulnerability is rated as an Important severity because an argument injection has been discovered in go-git, where an attackers can manipulate git-upload-pack flags, potentially enabling command or code execution leads to an exposure of sensitive data or other unintended actions, this vulnerability occurs…
| Product | Fixed in | Advisory |
|---|---|---|
| OADP-1.4-RHEL-9 | oadp/oadp-mustgather-rhel9:1.4.5-34 | RHSA-2025:11396 |
| 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 | grafana-0:10.2.6-9.el9_5 | RHSA-2025:3344 |
| 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 |
Frequently Asked Questions
Is CVE-2025-21613 in your dependencies?
O3 Security finds CVE-2025-21613 across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.