GitHacker is a tool that restores Git repositories from exposed .git directories. In 1.1.7 and earlier, add_head_file_tasks parses an attacker-controlled ref path from .git/HEAD and joins unvalidated path segments onto temp_dst/.git/logs/, allowing a malicious server to make GitHacker read an arbitrary local file when a victim runs the tool against the server's URL. add_hashes_parsed then scans the file for 40-character hexadecimal substrings and requests each match through .git/objects using the first two characters and remaining characters as path components, creating an attacker-observable existence oracle and disclosing matching hexadecimal fragments. Complete file contents are not returned, and the add_folder and add_task write path in shipped version 1.1.7 does not permit an escape. This issue is fixed in repository version 1.1.9.
CVE-2026-50024
This medium-severity CVE scores 5.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 62% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.3
- EG Score
- 5.3(medium)
- EG Risk
- 39(Track)EG Risk 39/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity53% × 45%Exploitation0% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 38%
- KEV
- Not listed
Published
September 9, 2026
Last Modified
September 16, 2026
Advisory Details (4)
Auto-updated Sep 15, 2026commit 5f2a8ba4d451 (WangYihang/GitHacker)
Fix landed in WangYihang/GitHacker commit 5f2a8ba4d451 — awaiting tagged release
https://github.com/WangYihang/GitHacker/commit/5f2a8ba4d451c6a1a465893507fbc42535a9d8c8commit 16fcd81a9c3d (WangYihang/GitHacker)
Fix landed in WangYihang/GitHacker commit 16fcd81a9c3d — awaiting tagged release
https://github.com/WangYihang/GitHacker/commit/16fcd81a9c3dfdf39713fde360d4e8bc3acf99e7fix: sanitize ref path in add_head_file_tasks to prevent path traversal
Upstream fix in progress (PR #65 · WangYihang/GitHacker, state=closed)
https://github.com/WangYihang/GitHacker/pull/65Path traversal in GitHacker ref/hash parsing enables existence oracle and hex-fragment exfiltration via a malicious .git server · Advisory · WangYihang/GitHacker · GitHub
Affected: 1.1.8 (commit
https://github.com/WangYihang/GitHacker/security/advisories/GHSA-hr3m-4qwq-3mgcVendor Advisories for CVE-2026-50024(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
PyPI(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| githacker | 1.0.1 ... 1.1.7 (17 versions) | 1.1.8 | — |
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 7× in last 7d / 8× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-18 21:19 UTCEG score recompute
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-17 20:14 UTCEG score recompute
- 2026-09-16 16:56 UTCEG score recompute
- 2026-09-16 15:55 UTCEG score recompute
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-15 16:35 UTCEG score recompute
- 2026-09-09 18:24 UTCEG score recompute
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-50024?
When was CVE-2026-50024 disclosed?
Is CVE-2026-50024 actively exploited?
What is the CVSS score of CVE-2026-50024?
How do I remediate CVE-2026-50024?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-50024
Is Your Infrastructure Affected by CVE-2026-50024?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.