CVE-2025-52569 GitHub.jl lacks validation for user-provided fields
Attackers can exploit missing input validation in GitHub.jl to perform path traversal and access unintended API endpoints on api.github.com.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2025-52569?
CVE-2025-52569 is a medium-severity path traversal vulnerability in JuliaWeb GitHub.jl, published on 25 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
GitForge.jl is a unified interface for interacting with Git "forges." Versions prior to 5.9.1 lack input validation of input validation for user-provided values in certain functions. In the `GitHub.repo()` function, the user can provide any string for the `repo_name` field. 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. Users should upgrade immediately to v5.9.1 or later to receive a patch. All prior versions are vulnerable. No known workarounds are available.
Which versions are affected by CVE-2025-52569?
How do I fix CVE-2025-52569?
Upgrade to a fixed version.
Upgrade, and resolve every user-supplied path against an allowed base folder before opening it. More about Path traversal.
Is CVE-2025-52569 being exploited?
There is no known exploitation of CVE-2025-52569 in the wild and no public exploit code.
Sources
Also known as GHSA-jg9p-c3wh-q83x, JLSEC-2025-5.