CVE-2026-45570: go-git Improper Single-quote Escaping Vulnerability

LOW
Advisory Identifier: GHSA-m7cr-m3pv-hgrp
CWE-116
Published
Advisory Summary

CVE-2026-45570 is a LOW improper single-quote escaping vulnerability (CWE-116: Improper Encoding or Escaping of Output) affecting go-git libraries in the Go ecosystem. The issue involves improper single-quote escaping in go-git ssh transport. Remediation is available by upgrading affected packages to version 5.19.1, 6.0.0-alpha.4.

CVE-2026-45570 at a Glance

CVE Identifier CVE-2026-45570
GHSA Identifier GHSA-m7cr-m3pv-hgrp
Severity LOW
CVSS v3.1 Base Score N/A
CWE Classification CWE-116: Improper Encoding or Escaping of Output
Affected Product go-git
Package Ecosystem Go
Published Date
Last Updated

How to Fix CVE-2026-45570

To remediate this vulnerability, upgrade all affected go-git dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/go-git/go-git/v5 fixed: 5.19.1
Upgrade github.com/go-git/go-git/v5 to 5.19.1
github.com/go-git/go-git/v6 fixed: 6.0.0-alpha.4
Upgrade github.com/go-git/go-git/v6 to 6.0.0-alpha.4
github.com/go-git/go-git fixed: Latest secure release
Upgrade github.com/go-git/go-git to Latest secure release
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for github.com/go-git/go-git/v5

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-45570, inspect your project dependencies for go-git:

inspect dependencies for github.com/go-git/go-git/v5

Analyze the terminal output to locate any version of go-git in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 5.19.1), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-116: Improper Encoding or Escaping of Output, where the product prepares a structured message for communication with another component, but encoding or escaping of the data is either missing or done incorrectly. as a result, the intended structure of the message is not preserved. In go-git, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Impact `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. This diverges from canonical Git, which shell-quotes the path through `sq_quote_buf` so that an embedded `'` becomes the `'\''` close-escape-reopen sequence and the whole path round-trips as a single quoted argument. 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. On SSH servers that evaluate the exec command through a shell (for example a user account whose login shell is `/bin/sh` or `/bin/bash`, or a `ForceCommand` wrapper that re-evaluates `$SSH_ORIGINAL_COMMAND`), those additional tokens execute in that account's command-execution context. SSH servers that tokenize the exec command without shell evaluation, including the canonical `git-shell` setup, are not affected. The vulnerable behaviour is on the SSH server side, not in `go-git`: the same bytes can be produced by any SSH client. The change in `go-git` is defense-in-depth that restores parity with canonical Git's wire format and prevents `go-git` from being a vehicle for reaching shell-evaluating servers through attacker-influenced repository paths. ### Patches Users should upgrade to a patched version in order to mitigate this issue. The fix ports `sq_quote_buf` from canonical Git into `go-git`'s SSH transport so that the wire output is byte-identical to what `git` itself would send for the same input. Versions prior to `v5` are likely to be affected, users are recommended to upgrade to a supported go-git version. ### Credit Thanks to @N0zoM1z0 for reporting this to the `go-git` project. :bow:

CVE-2026-45570 Affected go-git Versions

3 component(s)
Fixed Versions:
5.19.16.0.0-alpha.4
Product / Package Ecosystem Affected Versions Fixed Version
github.com/go-git/go-git/v5
Go
< 5.19.1
5.19.1
github.com/go-git/go-git/v6
Go
< 6.0.0-alpha.4
6.0.0-alpha.4
github.com/go-git/go-git
Go
≤ 4.7.0

References

Frequently Asked Questions

What is CVE-2026-45570?
CVE-2026-45570 is a security vulnerability in go-git involving Improper single-quote escaping in go-git SSH transport under CWE-116: Improper Encoding or Escaping of Output.
Which go-git versions are affected?
Affected versions include releases prior to 5.19.1, 6.0.0-alpha.4 across affected packages: github.com/go-git/go-git/v5, github.com/go-git/go-git/v6, github.com/go-git/go-git.
What version fixes CVE-2026-45570?
Upgrading to 5.19.1, 6.0.0-alpha.4 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/go-git/go-git/v5 affected?
Yes, github.com/go-git/go-git/v5 is affected in releases prior to 5.19.1. Upgrade your dependency to 5.19.1 or later.
Is github.com/go-git/go-git/v6 affected?
Yes, github.com/go-git/go-git/v6 is affected in releases prior to 6.0.0-alpha.4. Upgrade your dependency to 6.0.0-alpha.4 or later.
What CWE is associated with CVE-2026-45570?
CVE-2026-45570 is classified under CWE-116: Improper Encoding or Escaping of Output (The product prepares a structured message for communication with another component, but encoding or escaping of the data is either missing or done incorrectly. As a result, the intended structure of the message is not preserved.).
How can I check Go dependencies for CVE-2026-45570?
Run the dependency tree command: 'inspect dependencies for github.com/go-git/go-git/v5'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-m7cr-m3pv-hgrp",
  "modified" : "2026-06-08T23:42:58Z",
  "published" : "2026-05-19T15:21:01Z",
  "aliases" : [ "CVE-2026-45570" ],
  "summary" : "go-git: Improper single-quote escaping in go-git SSH transport",
  "details" : "### Impact\n\n`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. This diverges from canonical Git, which shell-quotes the path through `sq_quote_buf` so that an embedded `'` becomes the `'\\''` close-escape-reopen sequence and the whole path round-trips as a single quoted argument.\n\nA 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. On SSH servers that evaluate the exec command through a shell (for example a user account whose login shell is `/bin/sh` or `/bin/bash`, or a `ForceCommand` wrapper that re-evaluates `$SSH_ORIGINAL_COMMAND`), those additional tokens execute in that account's command-execution context. SSH servers that tokenize the exec command without shell evaluation, including the canonical `git-shell` setup, are not affected.\n\nThe vulnerable behaviour is on the SSH server side, not in `go-git`: the same bytes can be produced by any SSH client. The change in `go-git` is defense-in-depth that restores parity with canonical Git's wire format and prevents `go-git` from being a vehicle for reaching shell-evaluating servers through attacker-influenced repository paths.\n\n### Patches\n\nUsers should upgrade to a patched version in order to mitigate this issue. The fix ports `sq_quote_buf` from canonical Git into `go-git`'s SSH transport so that the wire output is byte-identical to what `git` itself would send for the same input.\n\nVersions prior to `v5` are likely to be affected, users are recommended to upgrade to a supported go-git version.\n\n### Credit\n\nThanks to @N0zoM1z0 for reporting this to the `go-git` project. :bow:",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:L"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/go-git/go-git/v5"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "5.19.1"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 5.19.0"
    }
  }, {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/go-git/go-git/v6"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "6.0.0-alpha.4"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 6.0.0-alpha.3"
    }
  }, {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/go-git/go-git"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "last_affected" : "4.7.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/go-git/go-git/security/advisories/GHSA-m7cr-m3pv-hgrp"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-45570"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/go-git/go-git"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-116" ],
    "severity" : "LOW",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-05-19T15:21:01Z",
    "nvd_published_at" : "2026-05-27T15:16:30Z"
  }
}