← Back
CVE-2026-44973
high
CVSS 8.1
Path Traversal in github.com/go-git/go-billy/v5 (CVE-2026-44973)
Summary
path traversal in github.com/go-git/go-billy/v5 (CVE-2026-44973). Confidential information can be exposed externally. Exploitable via ``osfs.ChrootOS``. Mitigation: upgrade to `5.9.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-44973** has been found in github.com/go-git/go-billy/v5.
Attackers can target a specific entry point like ``osfs.ChrootOS`` over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 8.1/10.
What to do: upgrade github.com/go-git/go-billy/v5 to **5.9.0** or later.
If unsure, ask your IT team or search "github.com/go-git/go-billy/v5 CVE-2026-44973" on the vendor's site.
CVE-2026-44973 (github.com/go-git/go-billy/v5) — CWE-22 / CVSS v3 8.1
Attack vector: remote (network-reachable) / no user interaction
Attack surface: `osfs.ChrootOS` / `osfs.BoundOS` / `osfs`
Patched: `5.9.0` — 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
**Path traversal** (CWE-22) exists in github.com/go-git/go-billy/v5. Attackers reach the vulnerable code path via ``osfs.ChrootOS`` without authentication.
📍 Affected scope
github.com/go-git/go-billy/v5 — . Attack surface: `osfs.ChrootOS` / `osfs.BoundOS` / `osfs`.
🔥 Severity
Severity: High (CVSS 8.1/10). Confidential information can be exposed externally
🔧 How to fix
Update to **5.9.0**.
🛡️ 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-billy/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-billy/v5' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `github.com/go-git/go-billy/v5` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade github.com/go-git/go-billy/v5 to 5.9.0ステージング環境で 5.9.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
go
github.com/go-git/go-billy/v5
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"5.9.0"}]}]
go
github.com/go-git/go-billy/v6
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"6.0.0-alpha.1"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2026-44973
- package https://github.com/go-git/go-billy
- web https://github.com/go-git/go-billy/security/advisories/GHSA-qw64-3x98-g7q2
- web https://github.com/go-git/go-billy/releases/tag/v5.9.0
- web https://github.com/go-git/go-billy/releases/tag/v6.0.0-alpha.1
- web https://github.com/advisories/GHSA-qw64-3x98-g7q2