CVE-2025-52483: JuliaRegistries Registrator.jl · Command Injection
Affects JuliaRegistries Registrator.jlSource CVE Database V5
Not known to be exploited · CVSS 8.1 High : upgrade to 1.9.5 soon.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 37% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.9.5
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:UExploitation evidence
Disclosed: evidence found.
CVE published 25 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
Upgrade juliaregistries/Registrator.jl to 1.9.5.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubjuliaregistries/Registrator.jlpkg:github/juliaregistries/Registrator.jlOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
European organizations should immediately upgrade all instances of Registrator.jl to version 1.9.5 or later to remediate this vulnerability. Since no workarounds exist, patching is the only effective mitigation. Additionally, organizations should audit their CI/CD pipelines and package registration workflows to identify any usage of vulnerable Registrator.jl versions. Implement network-level protections such as restricting outbound connections from build environments to only trusted sources to reduce exposure to malicious clone URLs. Employ runtime monitoring and anomaly detection to identify suspicious command executions or unexpected network activity originating from build or registry automation systems. Review and harden access controls around systems running Registrator.jl to limit potential lateral movement in case of compromise. Finally, organizations should consider integrating supply chain security tools that verify package integrity and provenance to detect tampering early.
Description
Registrator is a GitHub app that automates creation of registration pull requests for julia packages to the General registry. Prior to version 1.9.5, if the clone URL returned by GitHub is malicious (or can be injected using upstream vulnerabilities) a shell script injection can occur within the `withpasswd` function. Alternatively, an argument injection is possible in the `gettreesha `function.either of these can then lead to a potential RCE. Users should upgrade immediately to v1.9.5 to receive a fix. All prior versions are vulnerable. No known workarounds are available.