BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-45570High confidence

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

go-git · go-git

Official source article: GitHub GHSA-M7CR-M3PV-HGRP ↗. Check the applicable product and release in the original source.

2.3LowCVSS 4.0
Recommended action
Patch only the product branches with a verified fix

Low technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 2 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityLowOperational priority:Low, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • EPSS is 0.43% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs go-git go-git and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: No default targetRemediation target: Normal maintenance

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 2 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

7 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 2 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcegolang-github-go-git-go-gitAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcegolang-github-go-git-go-gitAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcegolang-github-go-git-go-gitVendor fix publishedDebian records a fixed source-package version for this release.5.19.1-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcegolang-github-go-git-go-git-v6Vendor fix publishedDebian records a fixed source-package version for this release.6.0.0~alpha4-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcegolang-github-go-git-go-gitVendor fix publishedDebian records a fixed source-package version for this release.5.19.1-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcegolang-github-go-git-go-git-v6Vendor fix publishedDebian records a fixed source-package version for this release.6.0.0~alpha4-1Debian Security Tracker ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · esm-appsgolang-github-go-git-go-gitUnder evaluationCanonical reports that the package might be affected and still needs evaluation or fixing.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Open-source package ranges6 source-attributed ranges

These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.

Ecosystem and packageAffected rangeFirst fixed versionEvidence
Gogithub.com/go-git/go-gitSEMVER: introduced 0; last affected 4.7.0Not statedOSV record ↗aggregator derived · 10 Sep 2026
Gogithub.com/go-git/go-git/v5SEMVER: introduced 0; fixed 5.19.15.19.1OSV record ↗aggregator derived · 10 Sep 2026
Gogithub.com/go-git/go-git/v6SEMVER: introduced 0; fixed 6.0.0-alpha.46.0.0-alpha.4OSV record ↗aggregator derived · 10 Sep 2026
gogithub.com/go-git/go-git<= 4.7.0Not statedGitHub advisory ↗upstream repository advisory · 8 Jun 2026
gogithub.com/go-git/go-git/v5<= 5.19.05.19.1GitHub advisory ↗upstream repository advisory · 8 Jun 2026
gogithub.com/go-git/go-git/v6<= 6.0.0-alpha.36.0.0-alpha.4GitHub advisory ↗upstream repository advisory · 8 Jun 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2026-45570 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitygithub.com/go-git/go-git: go-git: Shell command injection in SSH transport
4 fixed

The vendor explicitly identifies these products or versions as containing the fix.

  • registry.redhat.io/rhacm2/multicluster-operators-subscription-rhel9@sha256:08ac6178a4179ce64be22aac553ba38755009f1f276fb3235cd4a10dc19b9d8b_ppc64le as a component of Red Hat Advanced Cluster Management for Kubernetes 2.17
  • registry.redhat.io/rhacm2/multicluster-operators-subscription-rhel9@sha256:77abb0f6fd05fec3ea3c399df7f68c0cfaca0edca3bbb35155cd9dda2ad6bc03_amd64 as a component of Red Hat Advanced Cluster Management for Kubernetes 2.17
  • registry.redhat.io/rhacm2/multicluster-operators-subscription-rhel9@sha256:b5dfad0a7fe6cd8a538f8f3fdccecdc7421ce58fdc297b3e305434e905e39a70_s390x as a component of Red Hat Advanced Cluster Management for Kubernetes 2.17
  • registry.redhat.io/rhacm2/multicluster-operators-subscription-rhel9@sha256:d820bc1846bb1f465f1248f57f39e59af414483f19cc4cc0c4a7576562041518_arm64 as a component of Red Hat Advanced Cluster Management for Kubernetes 2.17
Summary
A flaw was found in go-git, a library used for Git operations. The component responsible for secure shell (SSH) communication does not correctly handle special characters in repository paths. This oversight allows a remote attacker to manipulate the command executed on the server by including a specially crafted repository path. This could result in the appending of additional shell commands, potentially leading to unintended actions on the system.
Remediation
Before you apply this update, make sure all previously released errata that are relevant to your system are applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2026-32546

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

Low technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 2 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

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.

What

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.

Why

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

An attacker operating through a network path may attempt exploitation when the stated preconditions are met. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

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.

Why

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

An attacker operating through a network path may attempt exploitation when the stated preconditions are met. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
a network path → Improper Encoding or Escaping of Output → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
Passive interaction required
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Not a CVSS 4.0 base metric
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-116 ↗

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.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
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

Common Vulnerability Scoring System 4.0: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.ATPresentAttack requirements: A particular deployment or execution condition must be present.PRNonePrivileges required: The attacker does not need an account or existing privileges.UIPassiveUser interaction: A user must unknowingly interact with the vulnerable system.VCNoneVulnerable-system confidentiality: No direct loss is represented by this metric.VINoneVulnerable-system integrity: No direct loss is represented by this metric.VANoneVulnerable-system availability: No direct loss is represented by this metric.SCLowSubsequent-system confidentiality: A successful attack can cause a limited loss.SILowSubsequent-system integrity: A successful attack can cause a limited loss.SALowSubsequent-system availability: A successful attack can cause a limited loss.
Post-exploitation / living off the land
Stolen credentials, tokens and legitimate administration functions may provide continued access without deploying a large custom toolset.
NetworkUnauthenticatedCWE-116
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

Cyber Security Agency of Singapore · English · CSA-SB-20260603Security Bulletin 3 Jun 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 3 Jun 2026, published on 3 June 2026. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-018304go-git projectのgo-gitにおけるエンコードおよびエスケープに関する脆弱性

go-gitは純粋なGoで書かれた拡張可能なgit実装ライブラリです。5.19.1および6.0.0-alpha.4より前のバージョンでは、go-gitのSSHトランスポートはリモートのexecコマンドをリポジトリパスを単一引用符で囲む形で構築していましたが、パス内に埋め込まれた単一引用符をエスケープしていませんでした。そのため、単一引用符を含むリポジトリパスはexecコマンド内の引用符で囲まれた領域から抜け出し、追加のシェルトークンとして解釈される可能性がありました。この脆弱性は5.19.1および6.0.0-alpha.4で修正されています。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
go-git: < 5.19.1, >= 6.0.0-alpha.1, < 6.0.0-alpha.4
Fixed
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 27 May 2026 · Last source change 28 May 2026, 15:12 UTC · CWE-116 · Improper Encoding or Escaping of Output

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2026-32546
Product sourceCNA
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD enriched

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    < 5.19.1; >= 6.0.0-alpha.1, < 6.0.0-alpha.4 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    After
    < 5.19.1; >= 6.0.0-alpha.1, < 6.0.0-alpha.4 · Fixed: Before you apply this update, make sure all previously released errata that are relevant to your system are applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
    Red Hat Product Security ↗
  2. Vendor guidanceAuthoritative vendor guidance changed from remediation: access.redhat.com/CVE-2026-45570 to remediation: access.redhat.com/CVE-2026-45570.
    Before
    remediation: access.redhat.com/CVE-2026-45570
    After
    remediation: access.redhat.com/CVE-2026-45570
    Red Hat Product Security ↗
  3. Remediation statusRemediation status changed from Awaiting fix to Patch available.
    Before
    Awaiting fix
    After
    Patch available
    Red Hat Product Security ↗
  4. Affected versionsThe structured affected or fixed version information changed.
    Before
    rhacm2/multicluster-operators-subscription-rhel9 as a component of Red Hat Advanced Cluster Management for Kubernetes 2
    After
    Fixed: registry.redhat.io/rhacm2/multicluster-operators-subscription-rhel9@sha256:08ac6178a4179ce64be22aac553ba38755009f1f276fb3235cd4a10dc19b9d8b_ppc64le as a component of Red Hat Advanced Cluster Management for Kubernetes 2.17; registry.redhat.io/rhacm2/multicluster-operators-subscription-rhel9@sha256:77abb0f6fd05fec3ea3c399df7f68c0cfaca0edca3bbb35155cd9dda2ad6bc03_amd64 as a component of Red Hat Advanced Cluster Management for Kubernetes 2.17; registry.redhat.io/rhacm2/multicluster-operators-subscription-rhel9@sha256:b5dfad0a7fe6cd8a538f8f3fdccecdc7421ce58fdc297b3e305434e905e39a70_s390x as a component of Red Hat Advanced Cluster Management for Kubernetes 2.17; registry.redhat.io/rhacm2/multicluster-operators-subscription-rhel9@sha256:d820bc1846bb1f465f1248f57f39e59af414483f19cc4cc0c4a7576562041518_arm64 as a component of Red Hat Advanced Cluster Management for Kubernetes 2.17
    Red Hat Product Security ↗
  5. Vendor guidanceAuthoritative vendor guidance changed from remediation: access.redhat.com/CVE-2026-45570 to remediation: access.redhat.com/CVE-2026-45570.
    Before
    remediation: access.redhat.com/CVE-2026-45570
    After
    remediation: access.redhat.com/CVE-2026-45570
    Red Hat Product Security ↗
  6. Affected versionsThe structured affected or fixed version information changed.
    Before
    After
    rhacm2/multicluster-operators-subscription-rhel9 as a component of Red Hat Advanced Cluster Management for Kubernetes 2
    Red Hat Product Security ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release recorded from official guidance
ENISA EUVD · EUVD-2026-32546↗Red Hat Product Security security advisory↗CVE authority or vendor reference · GitHub GHSA-M7CR-M3PV-HGRP↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2026-45570 · cve.blacktree.nl