Description
Gitingest through 0.3.1 fails to properly validate hostnames in _validate_host, accepting any host with a git., gitlab., or github. prefix regardless of known-hosts list membership. Attackers can submit URLs with attacker-controlled hostnames to trigger outbound connections to arbitrary hosts and disclose GitHub personal access tokens via HTTP basic credentials.
References6
- github.com/coderamp-labs/gitingest
- github.com/coderamp-labs/gitingest/blob/4e259a02fe72115bee53827…
- github.com/coderamp-labs/gitingest/blob/4e259a02fe72115bee53827…
- github.com/coderamp-labs/gitingest/issues/592
- www.vulncheck.com/advisories/gitingest-prefix-based-git-host-ch…
- github.com/coderamp-labs/gitingest/issues/592
Metrics
- CVSS 3.1
-
7.4
HIGH
Score source: CNA
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N - CVSS 4.0
-
8.3
HIGH
Score source: CNA
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X - EPSS — exploit probability
- 0% percentile: 38 · as of 8 November 2026
- CWE
- CWE-918
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.