VYPR
High severity8.8NVD Advisory· Published Jun 10, 2026· Updated Jun 10, 2026

CVE-2026-52758

CVE-2026-52758

Description

Ghidra versions before 12.1 are vulnerable to SQL injection in BSim filter types, allowing attackers to manipulate PostgreSQL database data.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

Ghidra versions before 12.1 are vulnerable to SQL injection in BSim filter types, allowing attackers to manipulate PostgreSQL database data.

Vulnerability

Ghidra versions prior to 12.1 contain a SQL injection vulnerability within multiple BSim filter types. These types directly concatenate user-supplied values from network-received XML protocol messages into SQL queries without proper escaping or parameterization. Specifically, ExecutableNameBSimFilterType.java, PathStartsBSimFilterType.java, and NotExecutableNameBSimFilterType.java are affected, while Md5BSimFilterType is not due to strict regex enforcement [1].

Exploitation

An attacker needs network access to the BSim server and the ability to send crafted XML protocol messages. The attacker can inject arbitrary SQL code by providing malicious values within these messages. The atom.value is read from the XML, normalized only by trimming whitespace, and then directly appended to SQL statements in methods like gatherSQLEffect() without any sanitization or escaping [1].

Impact

Successful exploitation allows a remote attacker to inject arbitrary SQL into database queries. This can lead to the reading, modification, or deletion of any data stored within the BSim PostgreSQL database. In environments where BSim is deployed and shared, this vulnerability compromises all stored binary analysis data [2].

Mitigation

Ghidra version 12.1 and later include a fix for this vulnerability. Users are strongly advised to upgrade to a patched version. No workarounds are specified in the available references, and the vulnerability is not listed as part of the CISA KEV catalog at this time [1, 2].

AI Insight generated on Jun 10, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected products

1

Patches

0

No patches discovered yet.

Vulnerability mechanics

No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.

References

2

News mentions

1