dbcve.org
Go GitApplication · Go Git Project

CVE-2026-41506

HIGH · 7.4 CVSS v3.1 Published 2026-05-08
Fix available
A fix is available. Upgrade to 5.18.0 or later.
See remediation →
81/100
Remediation priority · High
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

go-git library prior to versions 5.18.0 and 6.0.0-alpha.2 contains a vulnerability where HTTP authentication credentials are leaked when the library follows redirects during smart-HTTP clone and fetch operations. This allows credentials to be transmitted to potentially untrusted redirect targets.

MitigationUpgrade go-git to version 5.18.0 or 6.0.0-alpha.2 or later to patch the credential leakage. Review logs for any evidence of credential exposure to unauthorized domains.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Go GitApplication
Affected:< 5.18.0= 6.0.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
None
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed go-git version
    Run 'go list -m all | grep go-git' in your project, or check your go.mod file for the go-git version entry, or inspect the binary/vendor dependencies if using a compiled tool.
    Affected if The version is below 5.18.0 or equals exactly 6.0.0 (6.0.0-alpha.2 and later are patched).
  2. Determine if HTTP authentication is in use
    Review your git configuration, environment variables (GIT_USERNAME, GIT_PASSWORD, or HTTP_USERNAME/HTTP_PASSWORD), or the remote URL format (https://user:pass@host). For programmatic usage, review code that sets Auth fields in the go-git client.
    Affected if HTTP-based authentication credentials are configured for clone or fetch operations.
  3. Confirm smart-HTTP protocol is active
    Check if your remote URLs use https:// or http:// protocols (smart-HTTP). For servers, verify git-http-backend or similar HTTP-based git services are handling clone/fetch requests.
    Affected if You are using HTTP or HTTPS remotes for git operations.
  4. Inspect network logs for credential leakage
    Capture network traffic or review HTTP access logs on your git server and any intermediate proxies. Look for requests to domains other than your intended git server that contain authentication headers or credentials in the URL.
    Affected if Credentials appear in requests to domains other than the originally intended git server.

You are affected if your go-git version is below 5.18.0 or exactly 6.0.0 and you perform HTTP-authenticated clone or fetch operations that may follow redirects to other domains.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 5.18.0 or later
Fixed in 5.18.0
Interim mitigation

Upgrade go-git to version 5.18.0 or 6.0.0-alpha.2 or later to patch the credential leakage. Review logs for any evidence of credential exposure to unauthorized domains.

Recommended fix High confidence

5.18.0

  1. Check the current version of go-git in use (e.g., via go.mod or go list -m all)
  2. Upgrade go-git to version 5.18.0 or later by running: go get github.com/go-git/go-git/[email protected]
  3. Run go mod tidy to update dependencies
  4. Verify the upgrade was successful by checking the installed version
  5. Test that git clone and fetch operations function correctly with HTTP authentication

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Go Git Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-41506 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-41506 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data