Quick answers
- Is CVE-2026-52757 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-52757 being exploited in the wild.
- How severe is CVE-2026-52757?
- Medium severity, with a CVSS score of 4.4, published 10 June 2026.
- Which products and versions are affected?
- National Security Agency Ghidra < 12.1.
- Is there a fix for CVE-2026-52757?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-52757 attacked?
- It is attacked with local access, in a network appliance.
- Am I affected by CVE-2026-52757?
- Check whether you run National Security Agency Ghidra at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A heap-use-after-free (UAF) vulnerability exists in the Ghidra decompiler's HighVariable::merge() function during the variable merging pass. The root cause is an asymmetric cleanup in the HighIntersectTest::highedgemap cache; when moveIntersectTests() is called, it may fail to remove reverse entries for a HighVariable, leaving orphaned pointers. When the associated HighVariable object is subsequently deleted via mergeInternal(), these stale pointers remain in the cache. A later call to moveIntersectTests() dereferences these pointers to read or write the 'flags' field of the freed memory. This is reachable via the standard Java-to-native IPC path when a user opens a binary in the decompiler view or uses analyzeHeadless. The issue is fixed in Ghidra version 12.1.
Affected products
- NSA Ghidra < 12.1
Timeline
- 2026-05-15: advisory: GitHub Security Advisory published by NSA
- 2026-06-10: disclosed: NVD publication date