Go GitApplication · Go Git Project
CVE-2025-21614
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedgo-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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidencego-git versions prior to v5.13 contain a DoS vulnerability where specially crafted responses from a malicious Git server can trigger resource exhaustion in clients, leading to denial of service.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Go GitApplication
< 5.13.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Locate go-git dependency in your projectSearch for 'go-git' in your go.mod file, vendor/modules.txt, or dependency lock filesAffected if go-git is present as a dependency
-
Identify the installed version of go-gitRun 'go list -m all | grep go-git' or check the version line in your go.mod file (format: module version, e.g., github.com/go-git/go-git/v5 v5.12.0)Affected if The version shown is earlier than v5.13.0 (such as v5.12.0, v5.11.0, etc.)
-
Verify if your application uses go-git for remote operationsSearch source code for calls to 'Clone', 'Fetch', 'Pull', or 'NewRemote' which connect to Git serversAffected if Your code makes remote Git connections using go-git
-
Check for untrusted Git server connectionsReview whether go-git connects to user-controlled or unverified Git servers (e.g., user-provided URLs, external APIs)Affected if Your application connects to Git servers you do not fully control or trust
You are affected if go-git version earlier than v5.13.0 is installed AND your application uses it to connect to remote Git servers, especially untrusted ones.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped5.13.0
Upgrade go-git to v5.13 or later to mitigate this vulnerability.
v5.13.0
- Run 'go get github.com/go-git/go-git/[email protected]' to upgrade to the fixed version
- Run 'go mod tidy' to update go.mod and go.sum files
- Verify the upgrade by checking the version: go list -m github.com/go-git/go-git/v5
- Rebuild and test your application to ensure compatibility with the new version
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Go Git
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,144.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-21614 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-21614 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data