CVE-2026-52758
SQL injection in Ghidra <12.1 via BSim protocol enables remote DB access.
WAF coverage: SQL injection. Signatures match well at the request layer.
Also consider: parameterized queries · ORM
Is CVE-2026-52758 being exploited?
Not confirmed. CVE-2026-52758 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.31% probability of exploitation in the next 30 days.
How severe is CVE-2026-52758?
CVE-2026-52758 is rated High with a CVSS score of 8.7. 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-52758?
Yes. A fix has been recorded for CVE-2026-52758. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-52758 affect?
CVE-2026-52758 affects Ghidra <12.1, PostgreSQL databases accessed via BSim protocol. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-52758?
Upgrade to 12.1+; apply patch; re-test DB integrity.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Attacker can read, modify, or delete data in PostgreSQL via BSim SQL injection.
Patch when possible
- affected>= 11.0 and < 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.