go-git: Credential leak via cross-host redirect in smart HTTP transport

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

4.7 · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:N/A:N

EPSS

• CVE-2026-41506: 0.26% estimated exploitation activity in the next 30 days; percentile 17.63 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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…

Published by the source

17 Apr 2026, 22:31 UTC

Last modified by the source

12 May 2026, 13:32 UTC

Source last checked

26 Oct 2026, 15:20 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-3xc5-wrhm-f963

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-41506

Advisory: go-git: Credential leak via cross-host redirect in smart HTTP transport
IDs: CVE-2026-41506, GHSA-3xc5-wrhm-f963
Record: https://patchnext.com/advisories/cve-2026-41506 (revision 1, source checked 26 Oct 2026, 15:20 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/go-git/go-git/v6 6.0.0-alpha.2; github.com/go-git/go-git/v5 5.18.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/go-git/go-git/v6: affected <= 6.0.0-alpha.1; fixed in 6.0.0-alpha.2
- Go github.com/go-git/go-git/v5: affected <= 5.17.2; fixed in 5.18.0

## Suggested inspection (read-only)
- Go github.com/go-git/go-git/v6: check the installed version with your package manager.
- Go github.com/go-git/go-git/v5: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/go-git/go-git/v6, github.com/go-git/go-git/v5.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-3xc5-wrhm-f963 (GitHub-reviewed advisory GHSA-3xc5-wrhm-f963 lists affected ranges: Go github.com/go-git/go-git/v5 >=0 =0 <=6.0.0-alpha.1)

Commands are suggestions: review each one before running it.