CVE-2025-50178

GitForge.jl lacks validation for user provided fields

MEDIUM
6.6
CVSS Score
Published: June 25, 2025 at 03:12 PM UTC
Updated: June 17, 2026 at 09:34 AM UTC
1 product affected across 1 vendorGitForge.jl

Using GitForge.jl by JuliaWeb?

Get instant alerts when new vulnerabilities affect GitForge.jl - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM6.6
Exploit prediction
EPSS 0.5%
SSVC
No known exploit

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

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 0.4.3
Affected range stops below 0.4.3, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

SSVC — Action Prioritization

SSVCNo known exploitAutomatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

6.6MEDIUMGitHub_M
Vector?

Quick Info

StatusDEFERRED
CWE
CWE-20CWE-22

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card