How severe is CVE-2025-21613?

No CVSS score has been assigned to CVE-2025-21613 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2025-21613?

CVE-2025-21613 affects the following packages: gopkg.in/src-d/go-git.v4 (Go), github.com/go-git/go-git/v5 (Go). Ecosystems affected: Go.

How do I fix CVE-2025-21613?

A fix is available for CVE-2025-21613; check the affected-versions list above or the advisory for the patched release of gopkg.in/src-d/go-git.v4, then make sure no transitive dependency still pins the vulnerable range.

How do I detect CVE-2025-21613 in my Go dependencies?

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.

How do I mitigate CVE-2025-21613 if there is no patch (or I can't update yet)?

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.

Is CVE-2025-21613 actively exploited in the wild?

No public exploit code has been indexed for CVE-2025-21613 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2025-21613?

CVE-2025-21613 has an EPSS (Exploit Prediction Scoring System) score of 1.3%, placing it in the 70th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2025-21613?

CVE-2025-21613 is classified as CWE-88 (CWE-88). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2025-21613 published, and has it been updated?

CVE-2025-21613 was published on January 6, 2025 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

Not in CISA KEV

CVE-2025-21613 — src-d/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

Also known asGHSA-v725-9546-7q7mGO-2025-3368

Published

Jan 6, 2025

Updated

Oct 28, 2026

Affected

2 pkgs

Patched

1 / 2

Exploits

None indexed

Exploitation data as of Nov 8, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

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

via FIRST.org ↗

1.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs70th percentile — riskier than 70% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

2 pkgs affected

🐹gopkg.in/src-d/go-git.v4🐹github.com/go-git/go-git/v5

Real-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

2 total 1 fixed

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.0`go get github.com/go-git/go-git/v5@v5.13.0`

Affected Products

1 product · 1 configurations

Application

go-gitgo-git_project

< 5.13.0

range

Detection & mitigation playbook

Open-source dependency

Detect
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
A fix is available for CVE-2025-21613; check the affected-versions list above or the advisory for the patched release of gopkg.in/src-d/go-git.v4, then make sure no transitive dependency still pins the vulnerable range.
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.

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.

Red HatImportant

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…

Workaround published by Red Hat

In cases where it is not possible to update to the latest version of go-git, it is recommended to enforce validation rules for values passed in the URL field.

Source: Red Hat security advisory for CVE-2025-21613 (CC BY 4.0)

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

### 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](https://git-scm.com/docs/git-upload-pack). 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 th