dbcve.org
Go GitApplication · Go Git Project

CVE-2026-45571

MEDIUM · 5.4 CVSS v3.1 Published 2026-05-27
Fix available
A fix is available. Upgrade to 5.19.1 or later.
See remediation →
61/100
Remediation priority · Elevated
Remotely reachable No privileges

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. Prior to 5.19.1 and 6.0.0-alpha.4, a path validation issue in go-git could allow crafted repository data to affect files outside the intended checkout target, including the repository's .git directory. These validations were introduced in upstream Git years ago, so the vulnerability arose from go-git drifting from those checks. This vulnerability is fixed in 5.19.1 and 6.0.0-alpha.4.

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

Path validation vulnerability in go-git allows crafted repository data to escape the intended checkout directory and write files outside the target path, including the repository's .git directory. The issue exists because go-git drifted from upstream Git by missing path traversal checks that were added to upstream Git years ago.

MitigationUpgrade go-git to version 5.19.1 or 6.0.0-alpha.4 or later to include the missing path validation checks.

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.19.1= 6.0.0

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L

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 version in go.mod
    Inspect the go.mod file in your project and look for a line starting with 'require' that contains 'github.com/go-git/go-git/v5' or 'github.com/go-git/go-git/v6', noting the version number after it.
    Affected if The version listed is less than 5.19.1 or equals exactly 6.0.0
  2. Check vendored go-git version
    If your project uses vendored dependencies, locate the go-git package in the vendor directory (typically vendor/github.com/go-git/go-git/) and check the version file or the module version in the vendor modules.txt.
    Affected if The vendored version is less than 5.19.1 or equals exactly 6.0.0
  3. Query installed go-git package
    Run 'go list -m github.com/go-git/go-git/v5' or 'go list -m github.com/go-git/go-git/v6' from your project directory to see the resolved version.
    Affected if The displayed version is less than 5.19.1 or equals exactly 6.0.0
  4. Determine if checkout operations are used
    Search your codebase for usage of go-git functions that perform checkout operations, such as Clone, Checkout, Pull, or Worktree operations that write files to the filesystem.
    Affected if Your application uses Clone, Checkout, or similar functions with user-controlled or untrusted repository data
  5. Check for binary dependencies
    If go-git is embedded in a compiled binary, use tools like 'strings' on the binary or a dependency analyzer to extract the linked go-git version string.
    Affected if The embedded go-git version is less than 5.19.1 or equals exactly 6.0.0

You are affected if your project uses go-git version less than 5.19.1 or exactly version 6.0.0 and performs checkout, clone, or similar operations on repositories, particularly those from untrusted sources.

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.19.1 or later
Fixed in 5.19.1
Interim mitigation

Upgrade go-git to version 5.19.1 or 6.0.0-alpha.4 or later to include the missing path validation checks.

Recommended fix High confidence

5.19.1 (for v5.x users) or 6.0.0-alpha.4 (for v6 alpha users)

  1. 1. Identify the current version of go-git in your project by checking go.mod or your dependency management
  2. 2. Run `go get github.com/go-git/go-git/v5@latest` to upgrade to the latest v5 release, or specify the exact version with `go get github.com/go-git/go-git/[email protected]`
  3. 3. For v6 alpha users, run `go get github.com/go-git/go-git/v6@latest` or `go get github.com/go-git/go-git/[email protected]`
  4. 4. Run `go mod tidy` to clean up dependencies
  5. 5. Rebuild and test your application to ensure the upgrade does not break existing functionality
Caveat Minor version upgrades may include API changes; review the go-git v5.19.1 and v6.0.0-alpha.4 release notes for any breaking changes before upgrading

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
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
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,096.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-45571 — 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-45571 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