go-git is an extensible git implementation library written in pure Go. Prior to versions 5.18.0 and 6.0.0-alpha.2, go-git may leak HTTP authentication credentials when following redirects during smart-HTTP clone and fetch operations. This issue has been patched in versions 5.18.0 and 6.0.0-alpha.2.
CVE-2026-41506
This medium-severity CVE scores 4.7 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 83% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
A fix is available — apply it.
- CVSS v3
- 4.7
- EG Score
- 4.7(medium)
- EPSS
- 17.5%
- KEV
- Not listed
Published
May 8, 2026
Last Modified
May 12, 2026
Advisory Details (3)
Auto-updated Jun 17, 2026Credential leak via cross-host redirect in smart HTTP transport · Advisory · go-git/go-git · GitHub
https://github.com/go-git/go-git/security/advisories/GHSA-3xc5-wrhm-f963v6.0.0-alpha.2
Patch available: go-git/go-git v6.0.0-alpha.2 (pre-release)
https://github.com/go-git/go-git/releases/tag/v6.0.0-alpha.2v5.18.0
Patch available: go-git/go-git v5.18.0
https://github.com/go-git/go-git/releases/tag/v5.18.0Vendor Advisories for CVE-2026-41506(2)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Patch Availability(1)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| redhat | syft-main-1.44.0-0.3.hum1 | 2026-05-14 | redhat |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(2 across 1 ecosystem)
Go(2)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| github.com/go-git/go-git/v5 | — | 5.18.0 | — |
| github.com/go-git/go-git/v6 | — | 6.0.0-alpha.2 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 8× in last 7d / 37× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
Showing the most recent 100 of 107 total refreshes for this CVE.
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:24 UTCEPSS rescore
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 02:29 UTCEPSS rescore
- 2026-07-18 10:04 UTCEPSS rescore
- 2026-07-16 17:03 UTCEPSS rescore
- 2026-07-16 05:49 UTCOSV refresh
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-13 22:30 UTCEPSS rescore
- 2026-07-13 06:13 UTCEPSS rescore
- 2026-07-13 06:13 UTCEPSS rescore
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-08 15:15 UTCEPSS rescore
- 2026-07-07 13:46 UTCEPSS rescore
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-04 06:31 UTCEPSS rescore
Show 75 moreShow fewer
- 2026-07-01 15:06 UTCEPSS rescore
- 2026-06-30 23:22 UTCEPSS rescore
- 2026-06-29 14:06 UTCEPSS rescore
- 2026-06-28 14:07 UTCEPSS rescore
- 2026-06-28 05:12 UTCVendor advisory
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-27 03:08 UTCEPSS rescore
- 2026-06-26 21:51 UTCVendor advisory
- 2026-06-25 13:49 UTCEPSS rescore
- 2026-06-25 13:49 UTCEPSS rescore
- 2026-06-24 14:05 UTCEPSS rescore
- 2026-06-23 21:33 UTCEPSS rescore
- 2026-06-22 14:25 UTCEPSS rescore
- 2026-06-22 14:25 UTCEPSS rescore
- 2026-06-21 14:56 UTCEPSS rescore
- 2026-06-21 14:56 UTCEPSS rescore
- 2026-06-21 01:59 UTCEPSS rescore
- 2026-06-19 19:25 UTCEPSS rescore
- 2026-06-18 17:52 UTCEPSS rescore
- 2026-06-18 17:52 UTCEPSS rescore
- 2026-06-17 17:53 UTCEPSS rescore
- 2026-06-17 02:08 UTCVendor advisory
- 2026-06-16 17:52 UTCEPSS rescore
- 2026-06-15 17:49 UTCEPSS rescore
- 2026-06-15 02:44 UTCVendor advisory
- 2026-06-14 03:14 UTCVendor advisory
- 2026-06-13 23:00 UTCEPSS rescore
- 2026-06-13 02:01 UTCVendor advisory
- 2026-06-12 23:12 UTCEPSS rescore
- 2026-06-12 23:12 UTCEPSS rescore
- 2026-06-12 02:33 UTCVendor advisory
- 2026-06-11 14:00 UTCEPSS rescore
- 2026-06-11 03:04 UTCVendor advisory
- 2026-06-10 22:18 UTCEPSS rescore
- 2026-06-10 13:22 UTCEPSS rescore
- 2026-06-10 13:22 UTCEPSS rescore
- 2026-06-10 03:35 UTCVendor advisory
- 2026-06-09 04:05 UTCVendor advisory
- 2026-06-08 14:17 UTCEPSS rescore
- 2026-06-08 14:17 UTCEPSS rescore
- 2026-06-08 04:36 UTCVendor advisory
- 2026-06-07 15:25 UTCEPSS rescore
- 2026-06-07 15:25 UTCEPSS rescore
- 2026-06-07 05:07 UTCVendor advisory
- 2026-06-06 13:47 UTCEPSS rescore
- 2026-06-06 13:47 UTCEPSS rescore
- 2026-06-06 05:39 UTCVendor advisory
- 2026-06-05 22:47 UTCEPSS rescore
- 2026-06-05 06:10 UTCEPSS rescore
- 2026-06-05 06:10 UTCEPSS rescore
- 2026-06-05 06:10 UTCVendor advisory
- 2026-06-04 13:12 UTCEPSS rescore
- 2026-06-04 13:12 UTCEPSS rescore
- 2026-06-04 06:39 UTCVendor advisory
- 2026-06-03 07:06 UTCVendor advisory
- 2026-06-02 20:13 UTCEPSS rescore
- 2026-06-02 07:37 UTCVendor advisory
- 2026-06-01 13:52 UTCEPSS rescore
- 2026-06-01 13:52 UTCEPSS rescore
- 2026-06-01 13:51 UTCEPSS rescore
- 2026-06-01 08:08 UTCVendor advisory
- 2026-05-31 22:30 UTCEPSS rescore
- 2026-05-31 22:30 UTCEPSS rescore
- 2026-05-31 00:16 UTCEPSS rescore
- 2026-05-31 00:16 UTCEPSS rescore
- 2026-05-31 00:16 UTCEPSS rescore
- 2026-05-29 13:44 UTCEPSS rescore
- 2026-05-29 13:44 UTCEPSS rescore
- 2026-05-28 13:44 UTCEPSS rescore
- 2026-05-28 13:44 UTCEPSS rescore
- 2026-05-28 13:44 UTCEPSS rescore
- 2026-05-27 13:40 UTCEPSS rescore
- 2026-05-27 13:40 UTCEPSS rescore
- 2026-05-27 13:40 UTCEPSS rescore
- 2026-05-26 13:44 UTCEPSS rescore
Related CVEs(same vendor + same CWE)
Same vendor
10 shownredhat
Same CWE
10 shownCWE-522
- CVE-2013-7055EG 9.8EPSS 93%CRITICAL
- CVE-2013-7052EG 9.8EPSS 98%CRITICAL
- CVE-2014-3445EG 9.8EPSS 92%CRITICAL
- CVE-2014-5381EG 9.8EPSS 94%CRITICAL
- CVE-2014-5093EG 9.8CRITICAL
- CVE-2016-4401EG 9.8CRITICAL
- CVE-2018-1000627EG 9.8CRITICAL
- CVE-2018-11742EG 9.8EPSS 96%CRITICAL
- CVE-2018-1000851EG 9.8CRITICAL
- CVE-2018-10824EG 9.8EPSS 96%CRITICAL
Frequently asked(5)
What is CVE-2026-41506?
When was CVE-2026-41506 disclosed?
Is CVE-2026-41506 actively exploited?
What is the CVSS score of CVE-2026-41506?
How do I remediate CVE-2026-41506?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-41506
Is Your Infrastructure Affected by CVE-2026-41506?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.