CVE-2026-41506: go-git: Credential leak via cross-host redirect in smart HTTP transport
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.
Published Apr 17, 2026 · Updated May 12, 2026
Affected packages
github.com/go-git/go-git/v5
- Ecosystem
- Go
- Affected
- <= 5.17.2
- Fixed in
- 5.18.0
- Check
go list -m github.com/go-git/go-git/v5
github.com/go-git/go-git/v6
- Ecosystem
- Go
- Affected
- <= 6.0.0-alpha.1
- Fixed in
- 6.0.0-alpha.2
- Check
go list -m github.com/go-git/go-git/v6
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
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. 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:
Credited to N0zoM1z0, AyushParkara, celinke97.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2026-71556
go-git: Worktree operations may follow symlinks
high7.1Aug 7, 2026CVE-2026-71557
go-git: Malicious reference names may modify files outside the reference storage
medium6.3Aug 7, 2026GHSA-w5pp-99ch-qj29
go-git: Malformed Git object data may cause panics or resource exhaustion
medium6.5May 29, 2026CVE-2026-45570
go-git: Improper single-quote escaping in go-git SSH transport
low2.3No fixMay 19, 2026CVE-2026-45571
go-git: Crafted repositories may modify main and submodule .git directories
medium5.4No fixMay 19, 2026CVE-2026-45022
go-git's improper parsing of specially crafted objects may lead to inconsistent interpretation compared to upstream Git
high7.0May 11, 2026
