Remote code execution via unsafe git arguments
Published Jun 25, 2025 · Updated Jun 26, 2025
Argument injection in Registrator.jl before 1.9.5 allows remote attackers to execute code through a malicious repository clone URL. The gettreesha() function passes the GitHub-supplied clone URL to an external git command without safely separating attacker-controlled text from command arguments. Exploitation requires GitHub to return a malicious clone URL, or an upstream flaw to inject one, and grants code execution in the Registrator service context.
Summary
What happened
Argument injection in Registrator.jl before 1.9.5 allows remote attackers to execute code through a malicious repository clone URL. The gettreesha() function passes the GitHub-supplied clone URL to an external git command without safely separating attacker-controlled text from command arguments. Exploitation requires GitHub to return a malicious clone URL, or an upstream flaw to inject one, and grants code execution in the Registrator service context.
The record
- CVE
- CVE-2025-52480
- Published
- Jun 25, 2025
- Updated
- Jun 26, 2025
- Vendor
- JuliaRegistries
- Product
- Registrator.jl
- Classifications
- CWE-88, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 25, 2025CVE publishedPublication date reported by the CVE source.
- Jun 26, 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=< 1.9.5
What conditions does exploitation require?
What is affected?
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