CVE-2025-50178
GitForge.jl lacks validation for user provided fields
Vexday Risk Score
13Low
SSVC decision (CISA)
Track
No exploitation signal → monitor
CVSS 6.6EPSS 0.4%KEV nãoPoC —Nuclei —Metasploit —Patch —
Lifecycle
25 Jun 2025Published on NVD
Recommendation: Monitor — no exploitation signal at the moment.
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.
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:U
Affected products
JuliaWeb · GitForge.jlWant to know if your infrastructure is exposed to this?
Talk to TrueHacking →