Skip to main content
No exploitation reportedFix available

CVE-2026-45571

No exploitation reported by the sources we read.

  • Published2026-05-27
  • Fixed in5.19.1
  • WeaknessCWE-22

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

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.

Timeline

dates in UTC
  1. 2026-05-2715:16CVE publishedNVD

Observed activity

isMalicious corpus · updated 2026-10-23 21:37 UTC
Indicators tagged with this CVE, per day0 indicators over 7 days
Block these indicators
  • Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2026-45571?format=txt
  • CSV export: https://api.ismalicious.com/edl/cve/CVE-2026-45571?format=csv
  • TAXII collection of exploited CVEs
  • The EDL and CSV take an API key on the Pro plan.

Versions per branch

NVD · OSV
Go-git project go-git
BranchAffectedFixed in
5.19< 5.19.15.19.1
6.0= 6.0.0no fix published
go-git/go-git
BranchAffectedFixed in
44.7≤ 44.7.0no fix published
go-git/go-git
BranchAffectedFixed in
6.0< 6.0.0-alpha.46.0.0-alpha.4

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Vendor advisories

  • CVE-2026-45571 Red Hat Product Security108 products fixed

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

  • RHSA-2026:37387 Red Hat Product Security108 products fixed

    Red Hat Security Advisory: Red Hat OpenShift Data Foundation 4.22.0 security, enhancement & bug fix update

Full record on NVD

Fix

  1. Update Go-git project go-git to 5.19.1
  2. Vendor fix Red Hat Product Security RHSA-2026:37387 · 108 productsBefore applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://docs.redhat.com/en/documentation/red_hat_openshift_data_foundation/4.22/html/updating_openshift_data_foundation/updating-ocs-…

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof-of-concept repositories
none listed
PoC-in-GitHub

Sources

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L
Published
2026-05-27
Last Modified
2026-06-17
NVD status
Analyzed
MSRC Title
go-git: Crafted repositories may modify main and submodule .git directories

Frequently asked questions

What is CVE-2026-45571?

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.

Is CVE-2026-45571 actively exploited?

Active exploitation of CVE-2026-45571 has not been confirmed. Its EPSS score was 0.3% on 2026-10-22, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2026-45571?

CVE-2026-45571 has a CVSS v3 base score of 5.4 (MEDIUM severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L.

Running go-git/go-git? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, October 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database