PT-2025-26838 · Unknown · Gitforge.Jl

Splitline · Published 2025-06-25 · Updated 2025-10-08 · CVE-2025-50178

Positive Technologies (AI Summary)

CVSS v4.0

6.6

Medium

Base vector

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

Name of the Vulnerable Software and Affected Versions: GitForge.jl versions prior to 0.4.3

Description: The issue is related to a lack of input validation for user-provided values in certain functions. Specifically, in the GitForge.get repo function for GitHub, the owner and repo fields can be manipulated by a user to access unintended endpoints on api.github.com by adding path traversal patterns like ../. This is possible because the inputs are not validated or safely encoded before being sent to the server.

Recommendations: For versions prior to 0.4.3, update to version 0.4.3 to resolve the issue. As a temporary workaround, consider validating and safely encoding user-provided inputs for the owner and repo fields in the GitForge.get repo function to prevent path traversal attacks.

Exploit

Fix

Path traversal

RCE

Weakness Enumeration

CWE-22

CWE-20

Related Identifiers

CVE-2025-50178

GHSA-G2XX-229F-3QJM

JLSEC-2025-3

Affected Products

Gitforge.Jl

References · 7

• 🔥 https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/50xxx/CVE-2025-50178.json · Exploit
• https://osv.dev/vulnerability/CVE-2025-50178 · Vendor Advisory
• https://nvd.nist.gov/vuln/detail/CVE-2025-50178 · Security Note
• https://osv.dev/vulnerability/JLSEC-2025-3 · Vendor Advisory
• https://github.com/JuliaWeb/GitForge.jl/pull/50 · Note
• https://github.com/JuliaWeb/GitForge.jl/security/advisories/GHSA-g2xx-229f-3qjm · Note
• https://twitter.com/CVEnew/status/1937898586731376859 · Twitter Post