go-git Credential leak via cross-host redirect in smart HTTP transport
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-41506
Publishedgo-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.
- Source published
- 8 May 2026 13:43:19 UTC
- Source modified
- 11 May 2026 18:50:50 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 · 4.7 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:N/A:N
euvd · EUVD-2026-28596
Publishedgo-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.
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: May 8, 2026, 1:43:19 PM
dateUpdated: May 11, 2026, 6:50:50 PM
22 related source bulletins · separate from aliases
openSUSE-SU-2026:11438-1: alloy-1.18.0-1.1 on GA media
CVE-2026-1229 · CVE-2026-33814 · CVE-2026-41506 · CVE-2026-41606 · CVE-2026-41607
SUSE-SU-2026:2468-1: Security update for amazon-ssm-agent
CVE-2025-22869 · CVE-2025-22870 · CVE-2025-47913 · CVE-2026-1229 · CVE-2026-25934 · CVE-2026-39821 · CVE-2026-39827 · CVE-2026-39828 · CVE-2026-39829 · CVE-2026-39830 · CVE-2026-39831 · CVE-2026-39832 · CVE-2026-39833 · CVE-2026-39834 · CVE-2026-39835 · CVE-2026-41506 · CVE-2026-42508 · CVE-2026-44740 · CVE-2026-46595 · CVE-2026-46597 · CVE-2026-46598
SUSE-SU-2026:22157-1: Security update for amazon-ssm-agent
CVE-2025-22869 · CVE-2025-22870 · CVE-2025-47913 · CVE-2026-1229 · CVE-2026-25934 · CVE-2026-39821 · CVE-2026-39827 · CVE-2026-39828 · CVE-2026-39829 · CVE-2026-39830 · CVE-2026-39831 · CVE-2026-39832 · CVE-2026-39833 · CVE-2026-39834 · CVE-2026-39835 · CVE-2026-41506 · CVE-2026-42508 · CVE-2026-44740 · CVE-2026-46595 · CVE-2026-46597 · CVE-2026-46598
openSUSE-SU-2026:10771-1: google-osconfig-agent-20260511.00-1.1 on GA media
CVE-2026-33186 · CVE-2026-41506
RHSA-2026:37387: Red Hat Security Advisory: Red Hat OpenShift Data Foundation 4.22.0 security, enhancement & bug fix update
CVE-2024-25621 · CVE-2024-40635 · CVE-2024-45310 · CVE-2025-8766 · CVE-2025-21613 · CVE-2025-21614 · CVE-2025-22870 · CVE-2025-47911 · CVE-2025-52881 · CVE-2025-54410 · CVE-2025-58058 · CVE-2025-64329 · CVE-2025-66506 · CVE-2026-22772 · CVE-2026-23831 · CVE-2026-24117 · CVE-2026-25680 · CVE-2026-25681 · CVE-2026-25934 · CVE-2026-27136 · CVE-2026-27141 · CVE-2026-27903 · CVE-2026-33540 · CVE-2026-33747 · CVE-2026-33748 · CVE-2026-33814 · CVE-2026-34986 · CVE-2026-35172 · CVE-2026-35469 · CVE-2026-39821 · CVE-2026-39827 · CVE-2026-39828 · CVE-2026-39829 · CVE-2026-39830 · CVE-2026-39831 · CVE-2026-39832 · CVE-2026-39833 · CVE-2026-39834 · CVE-2026-39835 · CVE-2026-39883 · CVE-2026-41506 · CVE-2026-41567 · CVE-2026-41568 · CVE-2026-42502 · CVE-2026-42506 · CVE-2026-42508 · CVE-2026-44740 · CVE-2026-45571 · CVE-2026-46595 · CVE-2026-46597 · CVE-2026-46598
SUSE-SU-2026:22558-1: Security update for google-osconfig-agent
CVE-2023-45288 · CVE-2025-22868 · CVE-2025-47911 · CVE-2025-58190 · CVE-2026-33186 · CVE-2026-33814 · CVE-2026-34986 · CVE-2026-39821 · CVE-2026-39827 · CVE-2026-39828 · CVE-2026-39829 · CVE-2026-39830 · CVE-2026-39831 · CVE-2026-39832 · CVE-2026-39833 · CVE-2026-39834 · CVE-2026-39835 · CVE-2026-41506 · CVE-2026-42508 · CVE-2026-46595 · CVE-2026-46597 · CVE-2026-46598
RHSA-2026:17669: Red Hat Security Advisory: Red Hat Hardened Images RPMs bug fix and enhancement update
CVE-2026-41506
openSUSE-SU-2026:10830-1: trivy-0.70.0-2.1 on GA media
CVE-2026-33814 · CVE-2026-41506
openSUSE-SU-2026:21899-1: Security update for alloy
CVE-2026-10722 · CVE-2026-1229 · CVE-2026-33814 · CVE-2026-39821 · CVE-2026-41506 · CVE-2026-41606 · CVE-2026-41607
SUSE-SU-2026:22242-1: Security update for google-osconfig-agent
CVE-2023-45288 · CVE-2024-45339 · CVE-2025-22868 · CVE-2025-47911 · CVE-2025-58190 · CVE-2026-33186 · CVE-2026-33814 · CVE-2026-34986 · CVE-2026-39821 · CVE-2026-39827 · CVE-2026-39828 · CVE-2026-39829 · CVE-2026-39830 · CVE-2026-39831 · CVE-2026-39832 · CVE-2026-39833 · CVE-2026-39834 · CVE-2026-39835 · CVE-2026-41506 · CVE-2026-42508 · CVE-2026-46595 · CVE-2026-46597 · CVE-2026-46598
openSUSE-SU-2026:21079-1: Security update for amazon-ssm-agent
CVE-2025-22869 · CVE-2025-22870 · CVE-2025-47913 · CVE-2026-1229 · CVE-2026-25934 · CVE-2026-39821 · CVE-2026-39827 · CVE-2026-39828 · CVE-2026-39829 · CVE-2026-39830 · CVE-2026-39831 · CVE-2026-39832 · CVE-2026-39833 · CVE-2026-39834 · CVE-2026-39835 · CVE-2026-41506 · CVE-2026-42508 · CVE-2026-44740 · CVE-2026-46595 · CVE-2026-46597 · CVE-2026-46598
openSUSE-SU-2026:10967-1: cheat-5.1.0-2.1 on GA media
CVE-2026-1229 · CVE-2026-39827 · CVE-2026-41506 · CVE-2026-42508 · CVE-2026-44740 · CVE-2026-46598
openSUSE-SU-2026:10803-1: git-bug-0.10.1-4.1 on GA media
CVE-2026-1229 · CVE-2026-41506
SUSE-SU-2026:2665-1: Security update for google-osconfig-agent
CVE-2026-33186 · CVE-2026-33814 · CVE-2026-34986 · CVE-2026-39821 · CVE-2026-39827 · CVE-2026-39828 · CVE-2026-39829 · CVE-2026-39830 · CVE-2026-39831 · CVE-2026-39832 · CVE-2026-39833 · CVE-2026-39834 · CVE-2026-39835 · CVE-2026-41506 · CVE-2026-42508 · CVE-2026-46595 · CVE-2026-46597 · CVE-2026-46598
SUSE-SU-2026:23853-1: Security update for alloy
CVE-2026-10722 · CVE-2026-1229 · CVE-2026-33814 · CVE-2026-39821 · CVE-2026-41506 · CVE-2026-41606 · CVE-2026-41607
openSUSE-SU-2026:10765-1: amazon-ssm-agent-3.3.4268.0-2.1 on GA media
CVE-2026-41506
openSUSE-SU-2026:20770-1: Security update for git-bug
CVE-2026-1229 · CVE-2026-41506
RHSA-2026:35111: Red Hat Security Advisory: Red Hat Hardened Images RPMs Security Update
CVE-2026-32285 · CVE-2026-41506 · CVE-2026-44740 · CVE-2026-46680 · CVE-2026-47262 · CVE-2026-48702 · CVE-2026-50195 · CVE-2026-53488
SUSE-SU-2026:22249-1: Security update for google-osconfig-agent
CVE-2023-45288 · CVE-2025-22868 · CVE-2025-47911 · CVE-2025-58190 · CVE-2026-33186 · CVE-2026-33814 · CVE-2026-34986 · CVE-2026-39821 · CVE-2026-39827 · CVE-2026-39828 · CVE-2026-39829 · CVE-2026-39830 · CVE-2026-39831 · CVE-2026-39832 · CVE-2026-39833 · CVE-2026-39834 · CVE-2026-39835 · CVE-2026-41506 · CVE-2026-42508 · CVE-2026-46595 · CVE-2026-46597 · CVE-2026-46598
SUSE-SU-2026:23865-1: Security update for alloy
CVE-2026-10722 · CVE-2026-1229 · CVE-2026-33814 · CVE-2026-39821 · CVE-2026-41506 · CVE-2026-41606 · CVE-2026-41607
openSUSE-SU-2026:21210-1: Security update for google-osconfig-agent
CVE-2023-45288 · CVE-2025-22868 · CVE-2025-47911 · CVE-2025-58190 · CVE-2026-33186 · CVE-2026-33814 · CVE-2026-34986 · CVE-2026-39821 · CVE-2026-39827 · CVE-2026-39828 · CVE-2026-39829 · CVE-2026-39830 · CVE-2026-39831 · CVE-2026-39832 · CVE-2026-39833 · CVE-2026-39834 · CVE-2026-39835 · CVE-2026-41506 · CVE-2026-42508 · CVE-2026-46595 · CVE-2026-46597 · CVE-2026-46598
openSUSE-SU-2026:20809-1: Security update for trivy
CVE-2025-64702 · CVE-2025-69725 · CVE-2026-25934 · CVE-2026-33186 · CVE-2026-33747 · CVE-2026-33748 · CVE-2026-34986 · CVE-2026-39984 · CVE-2026-41506
- Source published
- May 8, 2026, 1:43:19 PM (timezone not stated)
- Source modified
- May 11, 2026, 6:50:50 PM (timezone not stated)
- Saved here
- 13 Nov 2026 15:59: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 · 4.7 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:N/A:N
nvd · CVE-2026-41506
Publishedgo-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.
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: Analyzed
Weakness classifications: CWE-522
Original publisher date fields
published: 2026-05-08T14:16:33.983
lastModified: 2026-11-11T20:10:00.273
2 source CPE criteria · context only
- cpe:2.3:a:go-git_project:go-git:*:*:*:*:*:go:*:*
- cpe:2.3:a:go-git_project:go-git:6.0.0:alpha1:*:*:*:go:*:*
The original JSON retains the logical configuration operators, exclusions and version bounds.
- Source published
- 8 May 2026 14:16:33 UTC
- Source modified
- 11 Nov 2026 20:10:00 UTC
- Saved here
- 12 Nov 2026 15:19:01 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 · 4.7 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:N/A:N
CVSS 3.1 · [email protected] · Primary · 7.4 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N
osv · GHSA-3xc5-wrhm-f963
Published### Impact `go-git` may leak HTTP authentication credentials when following redirects during smart-HTTP clone and fetch operations. If a remote repository responds to the initial `/info/refs` request with a redirect to a different host, go-git updates the session endpoint to the redirected location and reuses the original authentication for subsequent requests. This can result in the credentials (e.g. Authorization headers) being sent to an unintended host. An attacker controlling or influencing the redirect target can capture these credentials and potentially reuse them to access the victim’s repositories or other resources, depending on the scope of the credential. **Clients using `go-git` exclusively with trusted remotes (for example, GitHub or GitLab), and over a secure HTTPS connection, are not affected by this issue.** The risk arises when interacting with untrusted or misconfigured Git servers, or when using unsecured HTTP connections, which is not recommended. Such configurations also expose clients to a broader class of security risks beyond this issue, including credential interception and tampering of repository data. ### Patches Users should upgrade to `v5.18.0`, or `v6.0.0-alpha.2`, in order to mitigate this vulnerability. Versions prior to v5 are likely to be affected, users are recommended to upgrade to a supported `go-git` version. The patched versions add support for configuring [followRedirects](https://git-scm.com/docs/git-config#Documentation/git-config.txt-httpfollowRedirects). In line with upstream behaviour, the default is now `initial`, while users can opt into `FollowRedirects` or `NoFollowRedirects` programmatically. ### Credit Thanks to the 3 separate reports from @celinke97, @N0zoM1z0 and @AyushParkara. Thanks for finding and reporting this issue privately to the `go-git` project. :bow:
- Source published
- 17 Apr 2026 22:31:35 UTC
- Source modified
- 10 Sep 2026 03:50:42 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:N/UI:R/S:C/C:L/I:N/A:N
Publisher rating · MODERATE
osv · GO-2026-5105
PublishedGo-git: Credential leak via cross-host redirect in smart HTTP transport in github.com/go-git/go-git
- Source published
- 24 Jul 2026 18:35:55 UTC
- Source modified
- 8 Aug 2026 21:41:52 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.