CVE-2026-41506

MEDIUMNVD 4.74.7—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 4.7 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 82% 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).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
4.7EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 4.7Exploit: None knownExposed: 0

A fix is available — apply it.

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.

CVSS v3
4.7
EG Score
4.7(medium)
EG Risk
21(Track)
EG Risk 21/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity47% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
18%
KEV
Not listed

Published

May 8, 2026

Last Modified

May 12, 2026

Advisory Details (3)

Auto-updated Jun 17, 2026
Patch available. Sources: github_release, github.
github Patch Available

Credential 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-f963
github_release Patch Available

v6.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.2
github_release Patch Available

v5.18.0

Patch available: go-git/go-git v5.18.0

https://github.com/go-git/go-git/releases/tag/v5.18.0

Vendor Advisories for CVE-2026-41506(3)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatodf4/rook-ceph-rhel9-operator:17829342842026-07-09redhat
redhattrivy-main-0.72.0-0.1.hum12026-07-02redhat
redhatsyft-main-1.44.0-0.3.hum12026-05-14redhat

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

(6 across 4 ecosystems)
Debian:14(2)
PackageVulnerable rangeFixed inDependents
golang-github-go-git-go-git5.14.0-1, 5.16.2-1, 5.17.0-1, 5.17.1-15.19.1-1—
golang-github-go-git-go-git-v66~git20260305.2083cf94-1, 6~git20260305.2083cf94-2, 6~git20260305.2083cf94-36.0.0~alpha4-1—
Go(2)
PackageVulnerable rangeFixed inDependents
github.com/go-git/go-git/v5—5.18.0—
github.com/go-git/go-git/v6—6.0.0-alpha.2—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
golang-github-go-git-go-git5.11.0-1 ... 5.4.2-4 (13 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
golang-github-go-git-go-git5.14.0-1, 5.16.2-1, 5.17.0-1, 5.17.1-1, 5.19.1-1——

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 30× 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 187 total refreshes for this CVE.

  1. 2026-09-13 16:47 UTCEPSS rescore
  2. 2026-09-12 15:01 UTCEPSS rescore
  3. 2026-09-11 14:53 UTCOSV refresh
  4. 2026-09-11 14:53 UTCEPSS rescore
  5. 2026-09-11 09:37 UTCEPSS rescore
  6. 2026-09-10 09:34 UTCEPSS rescore
  7. 2026-09-08 22:00 UTCEPSS rescore
  8. 2026-09-07 16:01 UTCEPSS rescore
  9. 2026-09-06 13:47 UTCEPSS rescore
  10. 2026-09-04 05:06 UTCEPSS rescore
  11. 2026-09-02 14:12 UTCEPSS rescore
  12. 2026-09-01 13:53 UTCEPSS rescore
  13. 2026-09-01 04:39 UTCEPSS rescore
  14. 2026-08-30 19:17 UTCEPSS rescore
  15. 2026-08-30 01:22 UTCEPSS rescore
  16. 2026-08-28 21:41 UTCEPSS rescore
  17. 2026-08-27 14:25 UTCEPSS rescore
  18. 2026-08-26 14:46 UTCEPSS rescore
  19. 2026-08-25 13:49 UTCEPSS rescore
  20. 2026-08-23 19:20 UTCEG score recompute
  21. 2026-08-23 19:20 UTCVendor advisory
  22. 2026-08-23 00:19 UTCEPSS rescore
  23. 2026-08-21 23:49 UTCEPSS rescore
  24. 2026-08-20 22:55 UTCEPSS rescore
  25. 2026-08-19 17:03 UTCEPSS rescore
Show 75 more
  1. 2026-08-18 13:48 UTCEPSS rescore
  2. 2026-08-17 13:47 UTCEPSS rescore
  3. 2026-08-17 11:57 UTCEG score recompute
  4. 2026-08-17 11:57 UTCVendor advisory
  5. 2026-08-16 14:56 UTCEPSS rescore
  6. 2026-08-16 04:39 UTCEG score recompute
  7. 2026-08-16 04:39 UTCVendor advisory
  8. 2026-08-16 02:14 UTCEPSS rescore
  9. 2026-08-15 01:30 UTCEPSS rescore
  10. 2026-08-14 03:14 UTCEG score recompute
  11. 2026-08-14 03:14 UTCVendor advisory
  12. 2026-08-13 22:00 UTCEPSS rescore
  13. 2026-08-13 00:20 UTCEG score recompute
  14. 2026-08-13 00:20 UTCVendor advisory
  15. 2026-08-12 13:51 UTCEPSS rescore
  16. 2026-08-12 00:51 UTCEG score recompute
  17. 2026-08-12 00:51 UTCVendor advisory
  18. 2026-08-11 13:43 UTCEPSS rescore
  19. 2026-08-11 01:23 UTCEG score recompute
  20. 2026-08-11 01:23 UTCVendor advisory
  21. 2026-08-11 00:00 UTCEPSS rescore
  22. 2026-08-10 01:54 UTCEG score recompute
  23. 2026-08-10 01:54 UTCVendor advisory
  24. 2026-08-09 13:46 UTCEPSS rescore
  25. 2026-08-09 02:26 UTCEG score recompute
  26. 2026-08-09 02:26 UTCVendor advisory
  27. 2026-08-08 16:37 UTCEPSS rescore
  28. 2026-08-07 21:10 UTCEG score recompute
  29. 2026-08-07 21:10 UTCVendor advisory
  30. 2026-08-06 21:42 UTCEG score recompute
  31. 2026-08-06 21:42 UTCVendor advisory
  32. 2026-08-06 13:46 UTCEPSS rescore
  33. 2026-08-05 22:10 UTCEG score recompute
  34. 2026-08-05 22:10 UTCVendor advisory
  35. 2026-08-05 19:17 UTCEPSS rescore
  36. 2026-08-04 15:10 UTCEPSS rescore
  37. 2026-08-04 10:38 UTCEPSS rescore
  38. 2026-08-04 02:10 UTCEG score recompute
  39. 2026-08-04 02:10 UTCVendor advisory
  40. 2026-08-03 10:36 UTCEPSS rescore
  41. 2026-08-03 02:41 UTCVendor advisory
  42. 2026-08-02 03:12 UTCEG score recompute
  43. 2026-08-02 03:12 UTCVendor advisory
  44. 2026-08-02 02:27 UTCEPSS rescore
  45. 2026-08-01 04:16 UTCEPSS rescore
  46. 2026-07-30 16:28 UTCEPSS rescore
  47. 2026-07-30 01:30 UTCEPSS rescore
  48. 2026-07-28 15:36 UTCEPSS rescore
  49. 2026-07-27 14:13 UTCEPSS rescore
  50. 2026-07-26 14:54 UTCEPSS rescore
  51. 2026-07-26 14:54 UTCEPSS rescore
  52. 2026-07-25 14:18 UTCEPSS rescore
  53. 2026-07-24 14:17 UTCEPSS rescore
  54. 2026-07-23 14:18 UTCEPSS rescore
  55. 2026-07-23 03:11 UTCEG score recompute
  56. 2026-07-22 14:08 UTCEPSS rescore
  57. 2026-07-21 15:24 UTCEPSS rescore
  58. 2026-07-20 17:08 UTCEPSS rescore
  59. 2026-07-19 14:31 UTCEPSS rescore
  60. 2026-07-19 02:29 UTCEPSS rescore
  61. 2026-07-18 10:04 UTCEPSS rescore
  62. 2026-07-16 17:03 UTCEPSS rescore
  63. 2026-07-16 05:49 UTCOSV refresh
  64. 2026-07-15 16:57 UTCEPSS rescore
  65. 2026-07-15 16:57 UTCEPSS rescore
  66. 2026-07-15 02:00 UTCEPSS rescore
  67. 2026-07-13 22:30 UTCEPSS rescore
  68. 2026-07-13 06:13 UTCEPSS rescore
  69. 2026-07-13 06:13 UTCEPSS rescore
  70. 2026-07-12 05:46 UTCEPSS rescore
  71. 2026-07-11 08:27 UTCEPSS rescore
  72. 2026-07-09 19:10 UTCEPSS rescore
  73. 2026-07-08 15:15 UTCEPSS rescore
  74. 2026-07-07 13:46 UTCEPSS rescore
  75. 2026-07-06 16:27 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-41506?
CVE-2026-41506 is a medium vulnerability published on May 8, 2026. 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.
When was CVE-2026-41506 disclosed?
CVE-2026-41506 was first published in the National Vulnerability Database on May 8, 2026, with the most recent update on May 12, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-41506 actively exploited?
CVE-2026-41506 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 82.4% of all scored CVEs.
What is the CVSS score of CVE-2026-41506?
CVE-2026-41506 has a CVSS v3 base score of 4.7 (NVD).
How do I remediate CVE-2026-41506?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-41506, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-41506

Explore →

Is Your Infrastructure Affected by CVE-2026-41506?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs