Vulnerability in github.com/go-git/go-git/v5 (CVE-2026-41506)
Summary
Vulnerability in github.com/go-git/go-git/v5 (CVE-2026-41506). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 5.18.0 or later.
Original description
The description as published by the source.
Go-git: Credential leak via cross-host redirect in smart HTTP transport in github.com/go-git/go-git
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A weakness called CVE-2026-41506 was discovered in github.com/go-git/go-git/v5.
Severity is Medium (CVSS 4.7/10). Exploitation requires specific conditions but can cause real harm if successful.
What you should do: update the affected software to the latest version. If unsure, ask your IT team or search the vendor's site for "github.com/go-git/go-git/v5 CVE-2026-41506".
CVE-2026-41506 (github.com/go-git/go-git/v5). Severity: Medium / CVSSv3 4.7. Category: CWE-522.
Response plan:
- Check the vendor advisory for affected versions and the patched release.
- If a vulnerable version is running in production, schedule maintenance (urgency from KEV/CVSS).
- If no patch yet, mitigate via WAF rule, disabling the affected feature, etc.
- Monitor logs / SIEM for known IOC and PoC signatures of this CVE.
PoCs and fix commits: see the 'References' section, MITRE, and NVD.
A weakness (CVE-2026-41506) in github.com/go-git/go-git/v5. A serious software flaw has been identified.
Target versions of github.com/go-git/go-git/v5 (see vendor advisory). If running in production, identify exposure immediately.
Severity: Medium (CVSS 4.7/10). Exploitation requires specific conditions but can cause real harm if successful.
Update to the patched release as listed in the vendor advisory. (Typical mitigation pattern for CWE-522)
If a patch is not yet available, consider disabling the affected feature, applying WAF rules, blocking via network ACLs, or isolating the vulnerable version.
Check version information, scan dependencies via SBOM, and monitor SIEM for IOC and PoC signatures related to this CVE.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/go-git/go-git/v5' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/go-git/go-git/v5を grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade github.com/go-git/go-git/v5 to 5.18.0ステージング環境で 5.18.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2026-41506 golang-github-go-git-go-git
- Ubuntu UBUNTU-CVE-2026-41506 golang-github-go-git-go-git
References
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web github.com