GitHub.jl lacks validation for user-provided fields
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Attack requirements
- None
- Impact type
- Information disclosure
- Confidentiality · integrity · availability
- High · None · None
- Fix status
- Fixed
Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-22 and the CVSS impact.
Summary
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.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- Yes
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
Remediation
- Fix · CNA GitHub.jl (JuliaWeb) Fixed in 5.9.1
Timeline
- 2026-10-02 Threatist record created from CVE-2025-52569
References
More JuliaWeb vulnerabilities
- TI-2025-32606 HTTP.jl vulnerable to CR/LF Injection in URIs CVSS 4.0HIGH 7.7
- TI-2025-38120 HTTP.jl vulnerable to Header injection/Response splitting via header construction. CVSS 4.0HIGH 8.7
- TI-2025-32061 GitForge.jl lacks validation for user provided fields CVSS 4.0MEDIUM 6.6
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences