Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
GitHacker versions before 1.1.8 do not validate path segments parsed from a remote .git/HEAD file, so a malicious server can make it read arbitrary local files and then emit HTTP requests that reveal whether paths exist and leak 40-character hex fragments. An attacker must get a victim to run GitHacker against a URL the attacker controls. Upgrade to GitHacker 1.1.8, and run it inside a disposable container if you must use it against untrusted hosts.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 5.3 | Medium | 3.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0045, the 39th percentile, on 11 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:10 UTC First seen by agentprime
- 31 Oct 2026, 14:10 UTC Confirmed by OSV