CVE-2025-52480
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedRegistrator 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), an argument injection is possible in the `gettreesha()` function. This can then lead to a potential remote code execution. Users should upgrade immediately to v1.9.5 to receive a patch. All prior versions are vulnerable. No known workarounds are available.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceRegistator GitHub app versions prior to 1.9.5 contain an argument injection vulnerability in the gettreesha() function. When the clone URL returned by GitHub is malicious or manipulated through upstream vulnerabilities, attackers can inject arbitrary arguments leading to remote code execution.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 1.9.5CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm Registrator is installedLocate the Julialang Registrator installation in your environment. This is typically a Julia package used for package registration. Check your Julia package manager or project dependencies for the presence of Registrator.Affected if Registrator is found in the environment
-
Identify installed Registrator versionRun the Julia package manager command to query the installed version of Registrator, such as `] status Registrator` or checking your Project.toml/Manifest.toml file for the Registrator entry.Affected if The installed version is lower than 1.9.5
-
Verify GitHub integration is activeCheck if Registrator is configured to interact with GitHub for package registration. This typically involves checking environment variables (GITHUB_TOKEN), configuration files, or registration workflows that connect to GitHub.Affected if GitHub integration is enabled and Registrator interacts with GitHub repositories
-
Inspect gettreesha function usageReview any logs, traces, or code that calls the gettreesha() function within Registrator. This function processes clone URLs from GitHub and is the vulnerable component.Affected if The gettreesha() function is invoked with external GitHub clone URLs
You are affected if Registrator is installed with a version prior to 1.9.5 and has GitHub integration enabled, as the argument injection in gettreesha() can be triggered through malicious or manipulated clone URLs.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped1.9.5
Upgrade to version 1.9.5 immediately. No workarounds are available.
v1.9.5
- Identify the deployment method for Registrator (e.g., running from source, Docker container, or managed GitHub App)
- If running from source or Docker, update to version v1.9.5 by pulling the latest code or container image tagged v1.9.5
- Verify the fix from PR #449 has been applied: the gettreesha() function now properly sanitizes the clone URL before passing it to git commands
- Restart the Registrator service to load the updated version
- Confirm the version is 1.9.5 by checking the installed version or service metadata
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-52480 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-52480 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data