Security fix · CVE-2025-50178
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.
Published Jun 25, 2025 · catalog updated Jun 25, 2025 · JuliaWeb GitForge.jl
Last checked Oct 26, 2026. A connected source was read within the last 7 days.
Check if you run it
No confirmed exploitation is on record for CVE-2025-50178. EPSS is 0.47%. Act only if a listed version of JuliaWeb GitForge.jl is installed.
Gaps on this record
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
- Severity
- Medium6.6
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- 0.47%
- Remediation
- Version ranges on file
- Affected products
- vendor JuliaWeb GitForge.jl < 0.4.3
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 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.
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- vendor JuliaWeb GitForge.jl < 0.4.3< 0.4.3
How to fix CVE-2025-50178
Upgrade
CVE-2025-50178 lists a fix boundary at 0.4.3. Compare the installed build with that boundary before you change production.
Version check
Affected < 0.4.3
Advisory
Open the cve_org record and follow its fix.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
No confirmed exploitation is on record for CVE-2025-50178. EPSS is 0.47%. Act only if a listed version of JuliaWeb GitForge.jl is installed.
Which versions are affected?
Compare what you have installed with JuliaWeb GitForge.jl < 0.4.3 < 0.4.3. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
No weakness class is stored. EPSS 0.47%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Code
The project this record applies to. Exploit listings stay in References.
Timeline
Detection, updates, and resolution for this record.
Jun 25, 2025 · EUVD
Detected
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 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 th
Jun 25, 2025 · EUVD
Updated
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 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 th
Sources
- CVE.orgVulnerability recordCVE-2025-50178
Official CVE identifier
cve.org - FIRST EPSSExploitation probabilityCVE-2025-50178
30-day exploitation probability 0.47%
first.org - EUVDVulnerability recordEUVD-2025-28369
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 function for GitHub, the user can provide any string for the owner and repo fields. These inputs are not valid
euvd.enisa.europa.eu
References
Freshness
Last verified in this catalog Oct 26, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.
- FIRST EPSSOct 23, 2026
- CVE.orgOct 21, 2026
- EUVDOct 20, 2026