CVE-2026-52750
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 · uneditedGhidra before 12.1 contains a command injection vulnerability in URL annotation handling on Windows where cmd.exe metacharacters are not properly escaped. Attackers can execute arbitrary commands under the Ghidra user's privileges by embedding malicious URLs in program comments that victims click.
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 confidenceGhidra before 12.1 contains a command injection vulnerability in its URL annotation handling on Windows systems. When users click on malicious URLs embedded in program comments, the application fails to properly escape cmd.exe metacharacters, allowing arbitrary command execution under the Ghidra user's privileges.
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< 12.1CVSS 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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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 Windows platformVerify the operating system is Windows (this vulnerability only affects Windows installations)Affected if Running on Windows and Ghidra version is below 12.1
-
Identify installed Ghidra versionCheck the version by opening Ghidra and navigating to Help > About Ghidra, or inspect the installed directory name (typically Ghidra_12.x.x)Affected if Version is earlier than 12.1
-
Locate Ghidra installation directoryFind the Ghidra installation folder - commonly in Program Files or a custom directory - and verify the version from the folder nameAffected if The folder name indicates a version before 12.1
-
Check for program files with URLs in commentsOpen any previously analyzed binary files in Ghidra and inspect comments (EOL, plate, pre, post comments) for embedded URLsAffected if There are program comments containing URLs that could be clicked by a user
A user is affected if running Ghidra on Windows with version earlier than 12.1 and viewing/analyzing program files that contain URLs in comments that could be clicked.
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 · scoped12.1
Upgrade to Ghidra 12.1 or later to receive the patch. Until then, avoid clicking URLs in program comments from untrusted sources.
Ghidra 12.1
- Upgrade Ghidra to version 12.1 or later by downloading the latest release from the official GitHub repository (github.com/NationalSecurityAgency/ghidra)
- Verify the upgrade by checking Help > About Ghidra to confirm the version number
- After upgrading, test that URL annotations in comments function normally without executing arbitrary commands
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-52750 — 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-2026-52750 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