dbcve.org
GhidraApplication · Nsa

CVE-2026-52758

HIGH · 8.8 CVSS v3.1 Published 2026-06-10
Fix available
A fix is available. Upgrade to 12.1 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
Ghidra before 12.1 contains a SQL injection vulnerability in BSim filter types that concatenate user-supplied values directly into SQL queries without escaping or parameterization. Remote attackers can inject arbitrary SQL via the BSim network query protocol to read, modify, or delete data in the PostgreSQL database.

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 confidence

Ghidra before 12.1 contains a SQL injection vulnerability in BSim filter types where user-supplied values are concatenated directly into SQL queries without escaping or parameterization. Attackers can exploit this via the BSim network query protocol to execute arbitrary SQL commands against the PostgreSQL database.

MitigationUpgrade to Ghidra 12.1 or later. If immediate upgrade is not feasible, restrict network access to the BSim service and implement input validation as a temporary measure until the upgrade can be completed.

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
GhidraApplication
Affected:>= 11.0, < 12.1

CVSS 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Ghidra installation location and version
    Locate the Ghidra installation directory (commonly in /opt, ~/Downloads, or Program Files). Check the directory name for the version number (e.g., ghidra_11.0, ghidra_11.0.1). If installed, run 'ghidra 支持/version' or check for a version.properties file in the installation root.
    Affected if Ghidra version is 11.0 or higher but lower than 12.1, AND BSim with PostgreSQL is configured.
  2. Check if BSim database is configured
    Look for BSim configuration in the Ghidra user directory (typically ~/.ghidra/.ghidra_versions/bsim or within the Ghidra installation). Check for files containing PostgreSQL connection strings (host, port, database name, credentials). The BSim database is configured when a user creates or connects to a BSim database via the Ghidra BSim interface.
    Affected if A PostgreSQL database is configured for BSim functionality (the SQL injection can only be exploited against an active PostgreSQL connection).
  3. Verify BSim server/network service status
    Check if the BSim network query service is running. In Ghidra, BSim can be started as a server process. Look for running processes containing 'bsim' or check configured ports (default BSim server port is 23421). Check if the system is listening on the BSim port.
    Affected if The BSim network service is exposed and accessible to untrusted networks (this is the attack vector for the SQL injection).

A user is affected if they have Ghidra 11.0 through 12.0 installed, have configured a PostgreSQL database for BSim functionality, and the BSim network service is accessible to potential attackers.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 12.1 or later
Fixed in 12.1
Interim mitigation

Upgrade to Ghidra 12.1 or later. If immediate upgrade is not feasible, restrict network access to the BSim service and implement input validation as a temporary measure until the upgrade can be completed.

Recommended fix High confidence

Ghidra 12.1

  1. Download Ghidra 12.1 or later from the official GitHub releases page (github.com/NationalSecurityAgency/ghidra/releases)
  2. Replace the existing Ghidra installation with the updated version
  3. Restart any running Ghidra instances
  4. If using BSim with PostgreSQL, verify the database connection settings are properly configured in the new version
  5. Test that BSim queries function correctly after the upgrade
Caveat Review the Ghidra 12.1 release notes for any API changes that may affect custom scripts or extensions

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Ghidra Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-52758 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-52758 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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