{"id":"CVE-2025-50178","aliases":["EUVD-2025-28369","GHSA-g2xx-229f-3qjm","JLSEC-2025-3"],"status":"published","title":"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.","severity":{"version":"4.0","score":6.6,"vector":"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","level":"medium","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-12","score":0.00472,"percentile":0.41292,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-20","CWE-22"],"published":"2025-06-25T15:12:24Z","modified":"2026-10-28T02:30:26Z","fixes":[{"ecosystem":"Julia","package":"GitForge","fixed_in":["0.4.3"],"sources":["osv"]}],"affected":[{"source":"osv","ecosystem":"Julia","package":"GitForge","ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"0.4.3"}]}]}],"products":[{"vendor":"juliaweb","product":"gitforge.jl"}],"references":[{"url":"https://github.com/JuliaWeb/GitForge.jl/security/advisories/GHSA-g2xx-229f-3qjm","tags":["x_refsource_CONFIRM","advisory","web"]},{"url":"https://github.com/JuliaWeb/GitForge.jl/pull/50","tags":["x_refsource_MISC","fix","web"]},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/50xxx/CVE-2025-50178.json","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-50178","tags":["advisory"]}],"sources":{"cve":[{"id":"CVE-2025-50178","title":"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.","status":"published","published":"2025-06-25T15:12:24.751Z","modified":"2025-06-25T15:20:43.04Z","cvss":[{"version":"4.0","score":6.6,"vector":"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","level":"medium","assessor":"cna"}],"cwes":["CWE-20","CWE-22"],"updated_at":"2026-11-02T14:32:52.526476Z"}],"euvd":[{"id":"EUVD-2025-28369","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.","status":"published","published":"2025-06-25T15:12:24Z","modified":"2025-06-25T15:20:43Z","cvss":[{"version":"4.0","score":6.6,"vector":"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","level":"medium"}],"updated_at":"2026-11-02T20:32:16.561416Z"}],"nvd":[{"id":"CVE-2025-50178","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.","status":"published","published":"2025-06-25T16:15:26.693Z","modified":"2026-06-17T09:34:48.487Z","cvss":[{"version":"4.0","score":6.6,"vector":"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/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X","level":"medium","assessor":"secondary"}],"cwes":["CWE-20","CWE-22"],"updated_at":"2026-11-02T14:11:14.781314Z"}],"osv":[{"id":"CVE-2025-50178","title":"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.","status":"published","published":"2025-06-25T15:12:24.751Z","modified":"2026-10-28T02:30:26.259486168Z","cvss":[{"version":"4.0","score":6.6,"vector":"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","level":"medium"}],"cwes":["CWE-20","CWE-22"],"updated_at":"2026-11-02T15:44:50.037003Z"},{"id":"JLSEC-2025-3","title":"Lack of validation for user-provided fields in GitForge.jl","description":"### Description\n\nThere is a lack of input validation for user-provided values in certain functions.\n\nIn 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.\n\n### Impact\n\nThis 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.\n\n### Patches\n\nUsers should upgrade immediately to v0.4.3. All prior versions are vulnerable.\n\n### Workarounds\n\nNone\n\n### References\n\nFixed by: https://github.com/JuliaWeb/GitForge.jl/pull/50 (which is available in v0.4.3).\n\n### Credits\n\nThanks to *splitline* from the DEVCORE Research Team for reporting this issue.","status":"published","published":"2025-10-08T17:41:37.19Z","modified":"2026-07-18T03:30:04.476281364Z","cvss":[{"version":"4.0","score":6.6,"vector":"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/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X","level":"medium"}],"updated_at":"2026-11-02T15:47:17.805107Z"}]}}