GitForge.jl lacks validation for user provided fields
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.
- Products
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2025-50178
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 3 Nov 2026, 05:54 UTC · Revision 1
Source evidence
GitForge.jl lacks validation for user provided fields
core-osv · Original sourcePublished 25 Jun 2025, 15:12 UTC
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.
osv:CVE-2025-50178
Complete source record
{
"id": "8aa7bb0beae5ee8d5ec584a436dd936a4814204e7951ebef1e5486b598c4cb44",
"url": "https://osv.dev/vulnerability/CVE-2025-50178",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "GitForge.jl lacks validation for user provided fields",
"summary": "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.",
"evidence": "osv:CVE-2025-50178",
"products": [],
"severity": "medium",
"structured": {
"id": "CVE-2025-50178",
"aliases": [
"CVE-2025-50178",
"GHSA-g2xx-229f-3qjm",
"JLSEC-2025-3"
],
"metrics": [
{
"type": "CVSS_V4",
"score": "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": [
{
"ranges": [
{
"repo": "https://github.com/juliaweb/gitforge.jl",
"type": "GIT",
"events": [
{
"introduced": "0"
},
{
"fixed": "527332b8da1b729f390aabe895b00cc8869a1b64"
}
],
"database_specific": {
"extracted_events": [
{
"range": [
{
"introduced": "0"
},
{
"fixed": "0.4.3"
}
],
"source": "AFFECTED_FIELD",
"strategy": "StringRangeExpression"
},
{
"range": [
{
"introduced": "0"
},
{
"fixed": "0.4.3"
}
],
"source": "DESCRIPTION"
}
]
}
}
],
"versions": [
"v0.4.2",
"v0.4.1",
"v0.4.0",
"v0.3.0",
"v0.1.7",
"v0.2.9",
"v0.2.8",
"v0.2.7",
"v0.2.6",
"v0.2.5",
"v0.2.4",
"v0.2.3",
"v0.2.2",
"v0.2.1",
"v0.2.0",
"v0.1.6",
"v0.1.5",
"v0.1.4",
"v0.1.3",
"v0.1.2",
"v0.1.1",
"v0.1.0"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-50178.json"
}
}
],
"modified": "2026-10-28T02:30:26.259486168Z",
"provider": "osv",
"references": [
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/50xxx/CVE-2025-50178.json",
"https://github.com/JuliaWeb/GitForge.jl/security/advisories/GHSA-g2xx-229f-3qjm",
"https://nvd.nist.gov/vuln/detail/CVE-2025-50178",
"https://github.com/JuliaWeb/GitForge.jl/pull/50"
],
"provider_metadata": {
"cwe_ids": [
"CWE-20",
"CWE-22"
],
"cna_assigner": "GitHub_M",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/50xxx/CVE-2025-50178.json"
}
},
"related_cves": [
{
"value": "CVE-2025-50178",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 492882,
"published_at": "2025-06-25T15:12:24.751+00:00"
}