CVE-2025-50178 GitForge.jl lacks validation for user provided fields
Attackers can exploit missing input validation in GitForge.jl to perform path traversal and access unintended API endpoints on GitHub.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2025-50178?
CVE-2025-50178 is a medium-severity path traversal vulnerability in JuliaWeb GitForge.jl, published on 25 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official 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.
Which versions are affected by CVE-2025-50178?
How do I fix CVE-2025-50178?
Upgrade to a fixed version.
Upgrade, and resolve every user-supplied path against an allowed base folder before opening it. More about Path traversal.
Is CVE-2025-50178 being exploited?
There is no known exploitation of CVE-2025-50178 in the wild and no public exploit code.
Sources
Also known as GHSA-g2xx-229f-3qjm, JLSEC-2025-3.