Path Traversal in githacker (CVE-2026-50024)
Summary
Path traversal in githacker (CVE-2026-50024). Risk of unauthorized operations or information disclosure. Exploitable via GET. Mitigation: upgrade to 1.1.8 or later.
Original description
The description as published by the source.
Summary
GitHacker through 1.1.7 did not validate path segments parsed from attacker-controlled .git/HEAD before joining them onto its output directory. A malicious server could coerce GitHacker into reading arbitrary local files. Contents do not stream back wholesale, but the recovery loop turns any 40-character hex substring into an outbound HTTP GET — an existence oracle for arbitrary paths plus hex-fragment exfiltration of file contents.
Details
Vulnerability
GitHacker rebuilds a remote .git/ by fetching files into temp_dst. Two functions derived filesystem paths from server-controlled content:
add_head_file_tasksreads the downloaded.git/HEAD, parsesref:, and joins the raw ref-path ontotemp_dst/.git/logs/before reading the resulting file.add_hashes_parsedscans any file it reads for 40-character hex substrings and emitsGET .git/objects//for each one — onto the attacker's server and into the local output tree.
Pre-fix, add_head_file_tasks did not validate the ref segments. A malicious .git/HEAD of
ref: ../../../../../../etc/passwd
caused add_head_file_tasks to traverse out of temp_dst and read /etc/passwd. The bytes flowed into add_hashes_parsed, which emitted one outbound HTTP request per 40-char-hex match — observable on the attacker's logs.
Impact
PR #65 originally classified this as arbitrary local file read. Joint analysis during coordinated disclosure narrowed the primitive: file contents do…
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 vulnerability tracked as CVE-2026-50024 has been found in githacker.
Attackers can target a specific entry point like GET over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 5.3/10.
What to do: upgrade githacker to 1.1.8 or later.
If unsure, ask your IT team or search "githacker CVE-2026-50024" on the vendor's site.
CVE-2026-50024 (githacker) — CWE-22 / CVSS v3 5.3
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: GET / temp_dst / add_head_file_tasks / add_hashes_parsed
Patched: 1.1.8 — apply immediately
Workaround: Run GitHacker inside a disposable container.
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.
Path traversal (CWE-22) exists in githacker. Attackers reach the vulnerable code path via GET without authentication.
Check the vendor advisory for the affected versions of githacker. Attack surface: GET / temp_dst / add_head_file_tasks / add_hashes_parsed.
Severity: Medium (CVSS 5.3/10). Risk of unauthorized operations or information disclosure.
Update to 1.1.8.
Workaround: Run GitHacker inside a disposable container.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'githacker' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'githacker' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
githackerを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
Run GitHacker inside a disposable container.パッチが適用されるまでの応急処置として、Run GitHacker inside a disposable container. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade githacker to 1.1.8ステージング環境で 1.1.8 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。