Skip to content
Fencer Intel
medium 5.4

CVE-2026-45571 json

go-git: Crafted repositories may modify main and submodule .git directories

published 5mo ago modified last mo. also EUVD-2026-32544 , GHSA-crhj-59gh-8x96 , GO-2026-5336

cvss
5.4
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 22%
public exploits
0
none known

Summary

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.

Patch / fix

  • go github.com/go-git/go-git/v5 5.19.1
  • go github.com/go-git/go-git/v6 6.0.0-alpha.4
  • go-git_project go-git 5.19.1, 6.0.0-alpha.4
  • golang-github-go-git-go-git Debian 14 5.19.1-1
  • golang-github-go-git-go-git-v6 Debian 14 6.0.0~alpha4-1

debian advisories DEBIAN-CVE-2026-45571

  • govulncheck-vulndb SLES 16.0, SLES for SAP applications 16.0 0.0.20260727T201416-160000.1.1

suse advisories SUSE-SU-2026:23216-1SUSE-SU-2026:23227-1

  • govulncheck-vulndb openSUSE Leap 16.0 0.0.20260727T201416-160000.1.1
  • flux2-cli openSUSE Tumbleweed 2.8.8-1.1

opensuse advisories openSUSE-SU-2026:21551-1openSUSE-SU-2026:10831-1

  • packer Azure Linux 3.0 1.9.5-17

azure linux advisories AZL-88797

Azure Linux vulnerability data, Copyright (c) Microsoft Corporation, from https://github.com/microsoft/AzureLinuxVulnerabilityData via OSV, under the MIT licence; changed: normalised to fixed package versions per release. MIT

Is CVE-2026-45571 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-45571 updated cvss 5.4

github.com/go-git/go-git: go-git: Path validation flaw allows unauthorized file access

  • Red Hat Openshift Data Foundation 4.22 odf4/cephcsi-rhel9 1782932114, odf4/odf-cli-rhel9 1783537001, odf4/mcg-core-rhel9 1783536000, odf4/odf-drbd-rhel9 1783537392, odf4/odf-console-rhel9 1783537586, odf4/devicefinder-rhel9 1782932104, +21 more
    fixed: vendor fix RHSA-2026:37387
  • Red Hat Openshift Data Foundation 4.22 odf4/mcg-operator-bundle 1783538986, odf4/ocs-operator-bundle 1783539176, odf4/odf-operator-bundle 1783539513, odf4/cephcsi-operator-bundle 1783538908, odf4/odr-hub-operator-bundle 1783539596, odf4/rook-ceph-operator-bundle 1783539714, +10 more
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
5mo ago

Exploit prediction

0.30% chance of exploitation in the next 30 days, higher than 22% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 5.4 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L
GitHub 3.1 5.4 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L

Affected packages

ecosystem package affected fixed in
go github.com/go-git/go-git/v5
<5.19.1
5.19.1
go github.com/go-git/go-git/v6
<6.0.0-alpha.4
6.0.0-alpha.4
go github.com/go-git/go-git
<=44.7.0
 no fix listed

Affected products

  • go-git go-git

Classification

Weakness
  • CWE-22 Improper Limitation of a Pathname to a Restricted Directory

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.