CVE-2026-50024: CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in WangYihang GitHacker
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.
AI Analysis
Technical Summary
GitHacker versions up to 1.1.7 improperly limit pathname traversal in the add_head_file_tasks function by joining unvalidated path segments from the .git/HEAD ref path onto temp_dst/.git/logs/. This allows a malicious server to cause GitHacker to read arbitrary local files when a victim runs the tool against the server's URL. The add_hashes_parsed function then scans the file for 40-character hexadecimal substrings and requests each match through .git/objects, creating an existence oracle that discloses matching hexadecimal fragments. Complete file contents are not returned. The vulnerability is addressed in GitHacker version 1.1.9 by restricting path escapes in add_folder and add_task write paths.
Potential Impact
An attacker controlling a malicious server URL can cause GitHacker clients running vulnerable versions to read arbitrary local files on the client system. While full file contents are not disclosed, the attacker can confirm the existence of certain hexadecimal fragments, potentially leaking sensitive information. There is no impact on integrity or availability.
Mitigation Recommendations
Upgrade GitHacker to version 1.1.9 or later, where the path traversal vulnerability is fixed by proper path validation preventing escapes. No other mitigation is required as the fix is official and addresses the issue directly.
CVE-2026-50024: CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in WangYihang GitHacker
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.
CVSS v3.1
Score 5.3medium
Affected software
WangYihang
GitHacker
pkg:github/wangyihang/GitHackerRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
GitHacker versions up to 1.1.7 improperly limit pathname traversal in the add_head_file_tasks function by joining unvalidated path segments from the .git/HEAD ref path onto temp_dst/.git/logs/. This allows a malicious server to cause GitHacker to read arbitrary local files when a victim runs the tool against the server's URL. The add_hashes_parsed function then scans the file for 40-character hexadecimal substrings and requests each match through .git/objects, creating an existence oracle that discloses matching hexadecimal fragments. Complete file contents are not returned. The vulnerability is addressed in GitHacker version 1.1.9 by restricting path escapes in add_folder and add_task write paths.
Potential Impact
An attacker controlling a malicious server URL can cause GitHacker clients running vulnerable versions to read arbitrary local files on the client system. While full file contents are not disclosed, the attacker can confirm the existence of certain hexadecimal fragments, potentially leaking sensitive information. There is no impact on integrity or availability.
Mitigation Recommendations
Upgrade GitHacker to version 1.1.9 or later, where the path traversal vulnerability is fixed by proper path validation preventing escapes. No other mitigation is required as the fix is official and addresses the issue directly.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-06-02T22:46:02.580Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6aa9651655bf5e2cf502e92c
Added to database: 09/15/2026, 15:32:38 UTC
Last enriched: 09/15/2026, 16:17:13 UTC
Last updated: 09/15/2026, 22:24:42 UTC
Views: 4
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.