We use these services and cookies to improve your user experience. You may opt out if you wish, however, this may limit some features on this site.

Please see our statement on Data Privacy.

Crisp.chat (Helpdesk and Chat)

Ok

THREATINT
PUBLISHED

CVE-2025-50178

GitForge.jl lacks validation for user provided fields



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.

Reserved 2025-06-13 | Published 2025-06-25 | Updated 2025-06-25 | Assigner GitHub_M


MEDIUM: 6.6CVSS: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

Problem types

CWE-20: Improper Input Validation

CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

Product status

< 0.4.3
affected

References

github.com/...rge.jl/security/advisories/GHSA-g2xx-229f-3qjm

github.com/JuliaWeb/GitForge.jl/pull/50

cve.org (CVE-2025-50178)

nvd.nist.gov (CVE-2025-50178)

Download JSON

Share this page
https://cve.threatint.eu/CVE/CVE-2025-50178

Support options

Helpdesk Chat, Email, Knowledgebase