← Back
CVE-2026-45570
critical
CVSS 9.6
Vulnerability in github.com/go-git/go-git/v5 (CVE-2026-45570)
Summary
vulnerability in github.com/go-git/go-git/v5 (CVE-2026-45570). Successful exploitation can lead to full system takeover. Exploitable via ``sq_quote_buf``. Mitigation: upgrade to `5.19.1` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-45570** has been found in github.com/go-git/go-git/v5.
Attackers can target a specific entry point like ``sq_quote_buf`` over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 9.6/10.
What to do: upgrade github.com/go-git/go-git/v5 to **5.19.1** or later.
If unsure, ask your IT team or search "github.com/go-git/go-git/v5 CVE-2026-45570" on the vendor's site.
CVE-2026-45570 (github.com/go-git/go-git/v5) — CWE-116 / CVSS v3 9.6
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: `sq_quote_buf` / `ForceCommand` / `git`
Patched: `5.19.1` — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**A vulnerability** (CWE-116) exists in github.com/go-git/go-git/v5. Attackers reach the vulnerable code path via ``sq_quote_buf`` without authentication.
📍 Affected scope
github.com/go-git/go-git/v5 — . Attack surface: `sq_quote_buf` / `ForceCommand` / `git`.
🔥 Severity
Severity: Critical (CVSS 9.6/10). Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **5.19.1**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'github.com/go-git/go-git/v5' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
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 し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade github.com/go-git/go-git/v5 to 5.19.1ステージング環境で 5.19.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
go
github.com/go-git/go-git/v5
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"5.19.1"}]}]
go
github.com/go-git/go-git/v6
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"6.0.0-alpha.4"}]}]
go
github.com/go-git/go-git
[{"type":"SEMVER","events":[{"introduced":"0"},{"last_affected":"4.7.0"}]}]