dbcve.org
Go GitApplication · Go Git Project

CVE-2026-45570

CRITICAL · 9.6 CVSS v3.1 Published 2026-05-27
Fix available
A fix is available. Upgrade to 5.19.1 or later.
See remediation →
100/100
Remediation priority · Urgent
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, go-git's SSH transport constructs the remote exec command by wrapping the repository path in single quotes without escaping single quotes embedded inside the path. A repository path containing a single quote can therefore break out of the quoted region in the exec command and be appended as additional shell tokens. 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

go-git's SSH transport implements improper quote handling when constructing remote exec commands. The library wraps repository paths in single quotes but fails to escape single quotes within the path itself, enabling command injection where attacker-controlled path data can break out of the quoted context and inject arbitrary shell tokens.

MitigationUpgrade go-git to version 5.19.1 or 6.0.0-alpha.4 or later, which properly escapes single quotes in repository paths before embedding them in SSH commands.

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
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/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 version in use
    Run 'go list -m all' or inspect the go.mod file to find the installed go-git module version
    Affected if Version is less than 5.19.1 or exactly 6.0.0
  2. Confirm SSH transport is being used
    Search the codebase for SSH-based git operations: look for URLs starting with 'ssh://', 'git@' (SSH shorthand), or any code path that passes SSH URLs to git.Clone, git.Push, or git.Pull functions
    Affected if Repository operations use SSH transport to communicate with remote servers
  3. Determine source of repository paths
    Audit code that constructs or receives repository URLs - trace where the URL/path argument comes from (user input, config files, web requests, environment variables)
    Affected if Repository paths could contain single quotes and originate from untrusted or user-controlled sources without validation

Environment is affected if go-git version is below 5.19.1 (or exactly 6.0.0), SSH transport is used for git operations, and repository paths containing single quotes can be supplied from external or 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, which properly escapes single quotes in repository paths before embedding them in SSH commands.

Recommended fix High confidence

5.19.1 or 6.0.0-alpha.4

  1. Identify the current version of go-git in use by checking go.mod or running `go list -m github.com/go-git/go-git`
  2. For v5.x users: upgrade to version 5.19.1 or later by running `go get github.com/go-git/go-git/[email protected]` or `go get github.com/go-git/go-git/v5@latest`
  3. For v6.x users: upgrade to version 6.0.0-alpha.4 or later by running `go get github.com/go-git/go-git/v6@latest`
  4. Verify the upgrade was successful by running `go list -m github.com/go-git/go-git`
  5. Run `go mod tidy` to update dependencies
  6. Run existing tests to verify the upgrade does not break functionality: `go test ./...`

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
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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