CVE-2026-50024 GitHacker: Path traversal in ref/hash parsing enables existence oracle and hex-fragment exfiltration via malicious .git server
A malicious Git server can exploit path traversal in GitHacker to read local files and leak hexadecimal fragments via an existence oracle.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-50024?
CVE-2026-50024 is a medium-severity path traversal vulnerability in WangYihang GitHacker, published on 15 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
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.
Which versions are affected by CVE-2026-50024?
3 open source packages ship an affected version, including githacker.
| Package | Affected | Fixed in |
|---|---|---|
githacker PyPI | All versions | 1.1.8 |
githacker PyPI | All versions | 1.1.8 |
githacker PyPI | All versions | 1.1.8 |
How do I fix CVE-2026-50024?
Upgrade githacker to 1.1.8 or later.
Upgrade, and resolve every user-supplied path against an allowed base folder before opening it. More about Path traversal.
Is CVE-2026-50024 being exploited?
There is no known exploitation of CVE-2026-50024 in the wild and no public exploit code.
Sources
Also known as GHSA-hr3m-4qwq-3mgc, PYSEC-2026-3835.