Unintended API access via repository-name path traversal
Published Jun 25, 2025 · Updated Jun 25, 2025
Path traversal in JuliaWeb GitHub.jl before 5.9.1 allows remote attackers to access unintended GitHub API endpoints via crafted repository names. GitHub.repo interpolates repo_name into an API URL without validation or safe encoding, so ../ segments alter the requested endpoint path. Reachability requires a consuming application to pass attacker-controlled names, and exposed data remains bounded by the GitHub credentials used for the request.
Summary
What happened
Path traversal in JuliaWeb GitHub.jl before 5.9.1 allows remote attackers to access unintended GitHub API endpoints via crafted repository names. GitHub.repo interpolates repo_name into an API URL without validation or safe encoding, so ../ segments alter the requested endpoint path. Reachability requires a consuming application to pass attacker-controlled names, and exposed data remains bounded by the GitHub credentials used for the request.
The record
- CVE
- CVE-2025-52569
- Published
- Jun 25, 2025
- Updated
- Jun 25, 2025
- Vendor
- JuliaWeb
- Product
- GitHub.jl
- Classifications
- CWE-20, CWE-22
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 25, 2025CVE publishedPublication date reported by the CVE source.
- Jun 25, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 5.9.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo