go-git has an Argument Injection via the URL field

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

9.2 · CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:Clear · score source

EPSS

• CVE-2025-21613: 1.28% estimated exploitation activity in the next 30 days; percentile 70.01 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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.

Published by the source

6 Jan 2025, 16:16 UTC

Last modified by the source

6 Jan 2025, 18:43 UTC

Source last checked

26 Oct 2026, 15:08 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-v725-9546-7q7m

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-21613

Advisory: go-git has an Argument Injection via the URL field
IDs: CVE-2025-21613, GHSA-v725-9546-7q7m
Record: https://patchnext.com/advisories/cve-2025-21613 (revision 1, source checked 26 Oct 2026, 15:08 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.2)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Partial vendor fix; fixed versions by package: github.com/go-git/go-git/v5 5.13.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/go-git/go-git/v5: affected < 5.13.0; fixed in 5.13.0
- Go gopkg.in/src-d/go-git.v4: affected >= 4.0.0, <= 4.13.1

## Suggested inspection (read-only)
- Go github.com/go-git/go-git/v5: check the installed version with your package manager.
- Go gopkg.in/src-d/go-git.v4: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/go-git/go-git/v5, gopkg.in/src-d/go-git.v4.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-v725-9546-7q7m (GitHub-reviewed advisory GHSA-v725-9546-7q7m lists affected ranges: Go gopkg.in/src-d/go-git.v4 >=4.0.0 =0 <5.13.0)

Commands are suggestions: review each one before running it.