CVE-2026-52751
Ghidra 12.x unsafe deserialization enables unauth RCE via crafted ghidra:// project file.
Is CVE-2026-52751 being exploited?
Not confirmed. CVE-2026-52751 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.71% probability of exploitation in the next 30 days.
How severe is CVE-2026-52751?
CVE-2026-52751 is rated High with a CVSS score of 8.6. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-52751?
Yes. A fix has been recorded for CVE-2026-52751. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-52751 affect?
CVE-2026-52751 affects Ghidra < 12.1. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-52751?
Upgrade to 12.1+; avoid opening untrusted ghidra:// project files.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
RCE via deserializing untrusted Shared-Project RMI data when opening a project.
Patch when possible
- affected< 12.1
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.