CVE-2024-56074: gitingest · Link Following
Affects gitingestSource CVE Database V5
Not known to be exploited · CVSS 5.5 Medium.
Data as of 26 Oct 2026, 13:47 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 30% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:L/I:L/A:LExploitation evidence
Disclosed: evidence found.
CVE published 15 Dec 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubcyclotruc/gitingestpkg:github/cyclotruc/gitingestOther threats | Affected– | Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
To mitigate CVE-2024-56074, organizations should monitor for official patches or updates from the gitingest maintainers and apply them promptly once available. In the interim, restrict the use of gitingest to trusted inputs and environments to minimize exposure to crafted symbolic links. Implement strict input validation and sanitization to detect and block symbolic links pointing outside the base directory. Employ filesystem permissions and access controls to limit the ability of gitingest processes to follow or create symbolic links outside designated directories. Consider running gitingest in isolated or sandboxed environments with minimal privileges to reduce potential impact. Additionally, educate users and administrators about the risks of interacting with untrusted symbolic links and encourage cautious handling of files processed by gitingest. Continuous monitoring for anomalous file access patterns related to symbolic links can also help detect exploitation attempts.
Description
gitingest before 9996a06 mishandles symbolic links that point outside of the base directory.
References
- gitingest.com (opens in a new tab)
- github.com/cyclotruc/gitingest/pull/23 (opens in a new tab)
- github.com/cyclotruc/gitingest/commit/9996a06a94450497c1abb35997f5e6cbc9b571ff (opens in a new tab)
- github.com/cyclotruc/gitingest/blob/9996a06a94450497c1abb35997f5e6cbc9b571ff/src/ingest.py (opens in a new tab)
- github.com/cyclotruc/gitingest/blob/9996a06a94450497c1abb35997f5e6cbc9b571ff/src/ingest.py (opens in a new tab)