Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

go-git: Improper single-quote escaping in go-git SSH transport

CVSS 4.0 2.3 LOWEUVD CVSS 4.0 2.3 CVSS 4.0 · [email protected] · Secondary 2.3 LOWCVSS 3.1 · [email protected] · Primary 9.6 CRITICALCVSS_V4 Publisher rating LOWFixed by github.com/go-git/go-git/v5 5.19.1Fixed by github.com/go-git/go-git/v6 6.0.0-alpha.4osv · severity unknownFixed by github.com/go-git/go-git/v5 5.19.1Fixed by github.com/go-git/go-git/v6 6.0.0-alpha.4KEV status unknown

cve-program · CVE-2026-45570

Published

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.

Read the publisher's advisory

euvd · EUVD-2026-32546

Published

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.

Read the publisher's advisory

nvd · CVE-2026-45570

Published

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.

Read the publisher's advisory

osv · GHSA-m7cr-m3pv-hgrp

Published

### 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:

Read the publisher's advisory

osv · GO-2026-5496

Published

Improper single-quote escaping in go-git SSH transport in github.com/go-git/go-git

Read the publisher's advisory

Affected versions, risk and source history

cve-program · CVE-2026-45570

Published

go-git

Vendor product

Publisher's version information

Shown as published. These rules are not interpreted as NuGet package version ranges.

{
                    "vendor": "go-git",
                    "product": "go-git",
                    "versions": [
                        {
                            "version": "< 5.19.1",
                            "status": "affected"
                        },
                        {
                            "version": ">= 6.0.0-alpha.1, < 6.0.0-alpha.4",
                            "status": "affected"
                        }
                    ]
                }

Original source record · Cite this exact observation · Complete original publisher JSON

euvd · EUVD-2026-32546

Published

EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.

Original publisher date fields

datePublished: May 27, 2026, 2:59:17 PM

dateUpdated: May 28, 2026, 3:12:03 PM

3 related source bulletins · separate from aliases

RHSA-2026:67543: Red Hat Security Advisory: Red Hat Advanced Cluster Management for Kubernetes v2.17.2 security update

CVE-2026-41178 · CVE-2026-45570 · CVE-2026-56852 · CVE-2026-66780 · CVE-2026-71556 · CVE-2026-75899 · CVE-2026-75931 · CVE-2026-75975 · CVE-2026-76172 · CVE-2026-89060

msrc_CVE-2026-45570: go-git: Improper single-quote escaping in go-git SSH transport

CVE-2026-45570

openSUSE-SU-2026:10831-1: flux2-cli-2.8.8-1.1 on GA media

CVE-2026-45570 · CVE-2026-45571

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

nvd · CVE-2026-45570

Published

NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.

Source analysis status: Analyzed

Weakness classifications: CWE-116

Original publisher date fields

published: 2026-05-27T15:16:30.240

lastModified: 2026-06-17T10:52:13.177

4 source CPE criteria · context only
  • cpe:2.3:a:go-git_project:go-git:*:*:*:*:*:go:*:*
  • cpe:2.3:a:go-git_project:go-git:6.0.0:alpha1:*:*:*:go:*:*
  • cpe:2.3:a:go-git_project:go-git:6.0.0:alpha2:*:*:*:go:*:*
  • cpe:2.3:a:go-git_project:go-git:6.0.0:alpha3:*:*:*:go:*:*

The original JSON retains the logical configuration operators, exclusions and version bounds.

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

osv · GHSA-m7cr-m3pv-hgrp

Published

github.com/go-git/go-git/v5

Go

SEMVER · introduced 0 → fixed 5.19.1

github.com/go-git/go-git/v6

Go

SEMVER · introduced 0 → fixed 6.0.0-alpha.4

github.com/go-git/go-git

Go

SEMVER · introduced 0 → last_affected 4.7.0

Original source record · Cite this exact observation · Complete original publisher JSON

osv · GO-2026-5496

Published

github.com/go-git/go-git

Go

SEMVER · introduced 0

github.com/go-git/go-git/v5

Go

SEMVER · introduced 0 → fixed 5.19.1

github.com/go-git/go-git/v6

Go

SEMVER · introduced 0 → fixed 6.0.0-alpha.4

Original source record · Cite this exact observation · Complete original publisher JSON

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 16 Nov 00:16 UTC · 274 of 275 readable · 251 fully read · 18 waiting for GitHub's hourly limit · documentation 469/469 current