What’s Vulnerable › Vulnerabilities

CVE-2025-50178: GitForge.jl lacks validation for user provided fields

• Severity: medium (CVSS 6.6 v4.0)
• Exploited in the wild: not listed in CISA KEV
• EPSS: 0.5% probability of exploitation in the next 30 days
• Public exploit or detection template: none known
• Published: 2025-06-25 · updated 2026-06-17
• Weakness: CWE-20

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.

Affected products

• JuliaWeb GitForge.jl: before 0.4.3

References

• https://github.com/JuliaWeb/GitForge.jl/pull/50
• https://github.com/JuliaWeb/GitForge.jl/security/advisories/GHSA-g2xx-229f-3qjm

Get alerted when CVE-2025-50178 or the next vulnerability affects your stack