go-git: Malicious reference names may modify files outside the reference storage
Exploitation and risk
Source statusCISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.
Which CVEs have scores here?
This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.
No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.
cve-program · CVE-2026-71557
Publishedgo-git is an extensible git implementation library written in pure Go. Prior to 5.19.2 and 6.0.0-alpha.5, reference names are not sanitized before being used to construct on-disk paths under the reference storage directory, so a maliciously crafted reference name (for example containing directory-traversal sequences) can cause go-git to write files outside the intended reference storage directory. Versions 5.19.2 and 6.0.0-alpha.5 fix the issue.
- Source published
- 7 Aug 2026 16:41:31 UTC
- Source modified
- 7 Aug 2026 17:55:10 UTC
- Saved here
- 23 Oct 2026 15:48:27 UTC
- Source terms
- CVE Program Terms of Use
Original source record · Cite this exact observation · Complete original publisher JSON
Source: cve-program · CVE Program Terms of Use. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
CVSS 3.1 · 6.3 CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:H/A:L
euvd · EUVD-2026-54527
Publishedgo-git is an extensible git implementation library written in pure Go. Prior to 5.19.2 and 6.0.0-alpha.5, reference names are not sanitized before being used to construct on-disk paths under the reference storage directory, so a maliciously crafted reference name (for example containing directory-traversal sequences) can cause go-git to write files outside the intended reference storage directory. Versions 5.19.2 and 6.0.0-alpha.5 fix the issue.
Additional publisher context
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: Aug 7, 2026, 4:41:31 PM
dateUpdated: Aug 7, 2026, 5:55:10 PM
10 related source bulletins · separate from aliases
openSUSE-SU-2026:22032-1: Security update for alloy
CVE-2026-2303 · CVE-2026-37236 · CVE-2026-41178 · CVE-2026-45679 · CVE-2026-45680 · CVE-2026-45681 · CVE-2026-45683 · CVE-2026-45684 · CVE-2026-46600 · CVE-2026-48496 · CVE-2026-56852 · CVE-2026-56854 · CVE-2026-56855 · CVE-2026-71556 · CVE-2026-71557 · CVE-2026-75889 · CVE-2026-78662 · CVE-2026-81521 · CVE-2026-89090
RHSA-2026:68806: Red Hat Security Advisory: Red Hat Hardened Images RPMs bug fix and enhancement update
CVE-2026-63209 · CVE-2026-71557
openSUSE-SU-2026:11803-1: alloy-1.19.2-1.1 on GA media
CVE-2026-2303 · CVE-2026-37236 · CVE-2026-41178 · CVE-2026-45679 · CVE-2026-45680 · CVE-2026-45681 · CVE-2026-45683 · CVE-2026-45684 · CVE-2026-46600 · CVE-2026-48496 · CVE-2026-56852 · CVE-2026-56854 · CVE-2026-71556 · CVE-2026-71557 · CVE-2026-75889 · CVE-2026-75890 · CVE-2026-81521 · CVE-2026-89090
RHSA-2026:68808: Red Hat Security Advisory: Red Hat Hardened Images RPMs bug fix and enhancement update
CVE-2026-63209 · CVE-2026-71557
RHSA-2026:66208: Red Hat Security Advisory: Red Hat Hardened Images RPMs Security Update
CVE-2026-71556 · CVE-2026-71557
SUSE-SU-2026:24148-1: Security update for alloy
CVE-2026-2303 · CVE-2026-37236 · CVE-2026-41178 · CVE-2026-45679 · CVE-2026-45680 · CVE-2026-45681 · CVE-2026-45683 · CVE-2026-45684 · CVE-2026-46600 · CVE-2026-48496 · CVE-2026-56852 · CVE-2026-56854 · CVE-2026-56855 · CVE-2026-71556 · CVE-2026-71557 · CVE-2026-75889 · CVE-2026-78662 · CVE-2026-81521 · CVE-2026-89090
openSUSE-SU-2026:21884-1: Security update for amazon-ssm-agent
CVE-2026-56854 · CVE-2026-56855 · CVE-2026-71556 · CVE-2026-71557 · CVE-2026-78662
RHSA-2026:68281: Red Hat Security Advisory: Red Hat Hardened Images RPMs Security Update
CVE-2026-71557 · CVE-2026-88922
SUSE-SU-2026:4286-1: Security update for amazon-ssm-agent
CVE-2026-56854 · CVE-2026-56855 · CVE-2026-71556 · CVE-2026-71557 · CVE-2026-78662
msrc_CVE-2026-71557: go-git: Malicious reference names may modify files outside the reference storage
CVE-2026-71557
- Source published
- Aug 7, 2026, 4:41:31 PM (timezone not stated)
- Source modified
- Aug 7, 2026, 5:55:10 PM (timezone not stated)
- Saved here
- 13 Nov 2026 17:02:49 UTC
- Source terms
- ENISA EUVD · source terms and attribution apply
Original source record · Cite this exact observation · Complete original publisher JSON
Source: euvd · ENISA EUVD · source terms and attribution apply. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
EUVD CVSS 3.1 · 6.3 CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:H/A:L
nvd · CVE-2026-71557
Publishedgo-git is an extensible git implementation library written in pure Go. Prior to 5.19.2 and 6.0.0-alpha.5, reference names are not sanitized before being used to construct on-disk paths under the reference storage directory, so a maliciously crafted reference name (for example containing directory-traversal sequences) can cause go-git to write files outside the intended reference storage directory. Versions 5.19.2 and 6.0.0-alpha.5 fix the issue.
Additional publisher context
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: Awaiting Analysis
Weakness classifications: CWE-22
Original publisher date fields
published: 2026-08-07T17:17:10.833
lastModified: 2026-09-10T20:41:33.140
- Source published
- 7 Aug 2026 17:17:10 UTC
- Source modified
- 10 Sep 2026 20:41:33 UTC
- Saved here
- 25 Oct 2026 15:18:57 UTC
- Source terms
- NIST NVD usage terms; underlying source attribution retained
Original source record · Cite this exact observation · Complete original publisher JSON
Source: nvd · NIST NVD usage terms; underlying source attribution retained. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
CVSS 3.1 · [email protected] · Secondary · 6.3 CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:H/A:L
osv · GHSA-qgq7-7hm3-q39j
Published### Impact A path traversal issue in `go-git` could allow malicious reference names to access files outside the repository's intended reference storage. Loose references are stored under `.git/<reference-name>`. The reference name was previously used as a path without verifying that the resolved path remained within the reference storage. A name such as `refs/heads/../../config` could therefore resolve to unrelated repository metadata such as `.git/config` or `.git/HEAD`. A malicious Git server could advertise such a reference name. The name may also survive refspec mapping; for example, it could be mapped to `refs/remotes/origin/../../config` during a clone or fetch operation. This vulnerability affects filesystem-backed repositories using the `storage/filesystem` package and its `dotgit` reference storage. Users relying exclusively on the in-memory storage implementation, `storage/memory`, are not affected, because reference names are not resolved as filesystem paths. Exploitation requires an application using `go-git` with filesystem-backed storage to interact with a malicious Git server or otherwise process attacker-controlled reference names. ### Patches The issue has been addressed by validating reference names at the `dotgit` storage entry points and rejecting names whose resolved paths could escape the reference storage. Users of filesystem-backed storage should upgrade to a patched version. ### Workarounds Applications that exclusively use `storage/memory` are not affected and do not require a workaround for this vulnerability. For applications using filesystem-backed storage, avoid cloning from or fetching from untrusted Git servers until an upgrade is possible. Applications that directly construct or process reference names may also validate them before passing them to filesystem-backed `go-git` storage. Application-level validation should only be considered a temporary mitigation and does not replace upgrading to a patched version. ### References - Fixes: - https://github.com/go-git/go-git/pull/2247 - https://github.com/go-git/go-git/pull/2254 ### Credits Thanks to @Saku0512 for reporting this issue and @Sahana2524 for proposing the initial fix. 🙇
- Source published
- 7 Aug 2026 16:41:51 UTC
- Source modified
- 10 Sep 2026 03:50:53 UTC
- Saved here
- 24 Oct 2026 13:19:41 UTC
- Source terms
- GitHub Advisory Database · CC-BY-4.0
Original source record · Cite this exact observation · Complete original publisher JSON
Source: osv · GitHub Advisory Database · CC-BY-4.0. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
CVSS_V3 · CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:H/A:L
Publisher rating · MODERATE
osv · GO-2026-6214
PublishedPath traversal via crafted reference names in github.com/go-git/go-git
- Source published
- 18 Aug 2026 16:38:10 UTC
- Source modified
- 1 Sep 2026 03:55:58 UTC
- Saved here
- 24 Oct 2026 13:19:41 UTC
- Source terms
- OSV · upstream source license applies
Original source record · Cite this exact observation · Complete original publisher JSON
Source: osv · OSV · upstream source license applies. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.