dbcve.org
Go GitApplication · Go Git Project

CVE-2026-34165

MEDIUM · 5.0 CVSS v3.1 Published 2026-03-31
Fix available
A fix is available. Upgrade to 5.17.1 or later.
See remediation →
50/100
Remediation priority · Moderate

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 · unedited
go-git is an extensible git implementation library written in pure Go. From version 5.0.0 to before version 5.17.1, a vulnerability has been identified in which a maliciously crafted .idx file can cause asymmetric memory consumption, potentially exhausting available memory and resulting in a denial-of-service (DoS) condition. Exploitation requires write access to the local repository's .git directory, it order to create or alter existing .idx files. This issue has been patched in version 5.17.1.

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 confidence

A vulnerability in go-git versions 5.0.0 to before 5.17.1 allows a maliciously crafted .idx file to cause asymmetric memory consumption, potentially exhausting available memory and resulting in denial-of-service. Exploitation requires write access to the local repository's .git directory to create or modify .idx files.

MitigationUpgrade go-git to version 5.17.1 or later. If upgrade is not immediately feasible, restrict write access to .git directories and validate .idx files before processing.

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
Affected:>= 5.0.0, < 5.17.1

CVSS 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
Local
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:R/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify go-git library version
    Check your project's dependency file (go.mod) or list installed packages using 'go list -m all' or 'grep go-git' to find the exact version of github.com/go-git/go-git being used
    Affected if The version is 5.0.0 through 5.17.0 (any version >= 5.0.0 and < 5.17.1)
  2. Confirm go-git is used for repository operations
    Review your codebase to determine if the go-git library is imported and used to open or manipulate git repositories
    Affected if Your code imports and uses github.com/go-git/go-git to work with repositories
  3. Determine if .idx file parsing is reachable
    Inspect your application logic to see if it opens existing repositories and reads packfiles, as this triggers .idx file parsing. Look for calls to functions like 'OpenPackIndex' or repository operations that read git objects
    Affected if Your application opens and parses git repositories containing .idx files (packfile indexes)
  4. Check .git directory write permissions
    Review file system permissions on .git directories your application accesses. Use 'ls -la' or access control checks to verify if untrusted users or processes could write to these directories
    Affected if Untrusted users or processes have write access to .git directories that your application processes

You are affected if your environment uses go-git version 5.0.0 through 5.17.0, your application parses .idx files from repositories, and an attacker could write malicious .idx files to a .git directory your application accesses.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 5.17.1 or later
Fixed in 5.17.1
Interim mitigation

Upgrade go-git to version 5.17.1 or later. If upgrade is not immediately feasible, restrict write access to .git directories and validate .idx files before processing.

Recommended fix High confidence

go-git v5.17.1 or later

  1. Upgrade go-git to version 5.17.1 or later by updating your go.mod file or running: go get github.com/go-git/go-git/[email protected]
  2. Verify the upgrade by running: go list -m all | grep go-git
  3. Test your application to ensure the upgrade does not break existing functionality

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Go Git Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,680
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,288.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-34165 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-34165 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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