CVE-2025-21613: GO-2025-3368 - Argument Injection via the URL field in github.com/go-git/go-git

CVE-2025-21613 · Severity: low · CVSS 3.1 · Published 2025-01-07

Argument Injection via the URL field in github.com/go-git/go-git

Technologies: github.com/go-git/go-git/v4 (Go), github.com/go-git/go-git/v5 (Go), gopkg.in/src-d/go-git.v4 (Go). Vendors: Go.

Quick answers

Is CVE-2025-21613 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2025-21613 being exploited in the wild.
How severe is CVE-2025-21613?
Low severity, with a CVSS score of 3.1, published 7 January 2025.
Which products and versions are affected?
github.com/go-git/go-git/v4 (Go) SEMVER:introduced=4.0.0; github.com/go-git/go-git/v5 (Go) SEMVER:introduced=0,fixed=5.13.0; gopkg.in/src-d/go-git.v4 (Go) SEMVER:introduced=4.0.0, SEMVER:introduced=4.0.0,last_affected=4.13.1.
Is there a fix for CVE-2025-21613?
Yes. github.com/go-git/go-git/v5 (Go): upgrade to 5.13.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2025-21613?
Check whether you run github.com/go-git/go-git/v4 (Go), github.com/go-git/go-git/v5 (Go) or gopkg.in/src-d/go-git.v4 (Go) 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.

How to fix

  • github.com/go-git/go-git/v5 (Go): upgrade to 5.13.0 or later
    go get github.com/go-git/go-git/v5@v5.13.0

Affected products

  • github.com/go-git/go-git/v4 (Go) SEMVER:introduced=4.0.0
  • github.com/go-git/go-git/v5 (Go) SEMVER:introduced=0,fixed=5.13.0
  • gopkg.in/src-d/go-git.v4 (Go) SEMVER:introduced=4.0.0, SEMVER:introduced=4.0.0,last_affected=4.13.1

Identifiers

  • CVE-2025-21613
  • GHSA-v725-9546-7q7m
  • GO-2025-3368

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.