CVE-2025-50178: JuliaWeb GitForge.jl · Improper Input Validation
Affects JuliaWeb GitForge.jlSource CVE Database V5
Not known to be exploited · CVSS 6.6 Medium : upgrade to 0.4.3 when convenient.
Data as of 26 Oct 2026, 08:30 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 40% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 0.4.3
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:UExploitation evidence
Disclosed: evidence found.
CVE published 25 Jun 2025
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
Upgrade github.com/juliaweb/GitForge.jl to 0.4.3.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Gogithub.com/juliaweb/GitForge.jlpkg:golang/github.com/juliaweb/GitForge.jlOther 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
1. Immediate upgrade to GitForge.jl version 0.4.3 or later, which contains the patch addressing input validation and encoding issues. 2. Audit all internal and third-party tools or scripts that use GitForge.jl to ensure they are not running vulnerable versions. 3. Implement network-level monitoring and anomaly detection for unusual API request patterns targeting api.github.com, focusing on requests containing path traversal sequences. 4. Employ strict input validation and sanitization in any custom wrappers or extensions around GitForge.jl to prevent injection of malicious path components. 5. Restrict API tokens and credentials used by GitForge.jl clients to the minimum necessary scopes to limit potential data exposure. 6. Consider deploying Web Application Firewalls (WAFs) or API gateways that can detect and block path traversal attempts in outgoing API requests. 7. Educate development and DevOps teams about the risks of using outdated dependencies and the importance of timely patching. 8. For organizations with sensitive data, conduct a security review of all GitHub API interactions to identify and remediate any other potential input validation weaknesses.
Description
GitForge.jl is a unified interface for interacting with Git "forges." Versions prior to 0.4.3 lack input validation for user provided values in certain functions. In the `GitForge.get_repo` function for GitHub, the user can provide any string for the owner and repo fields. These inputs are not validated or safely encoded and are sent directly to the server. This means a user can add path traversal patterns like `../` in the input to access any other endpoints on api.github.com that were not intended. Version 0.4.3 contains a patch for the issue. No known workarounds are available.