# 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.

- **Severity:** Medium 6.6 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Jun 2025
- **Updated:** 25 Jun 2025
- **Also known as:** GHSA-jg9p-c3wh-q83x, JLSEC-2025-5

## 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.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory), CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2025-52569?


## How do I fix CVE-2025-52569?

Upgrade to a fixed version.

## Is CVE-2025-52569 being exploited?

There is no known exploitation of CVE-2025-52569 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-52569 and fix it if it is affected.

What it is: 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.
Exploitation: There is no known exploitation of CVE-2025-52569 in the wild and no public exploit code.

Affected product: JuliaWeb GitHub.jl. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-52569/ (Markdown: https://insights.sbomify.com/CVE-2025-52569/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-52569
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-52569
- OSV: https://osv.dev/vulnerability/CVE-2025-52569

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-52569/
Summaries are generated and may contain mistakes; the official description above is the record.