Quick answers
- Is CVE-2026-52750 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-52750 being exploited in the wild.
- How severe is CVE-2026-52750?
- High severity, with a CVSS score of 7.8, published 10 June 2026.
- Which products and versions are affected?
- National Security Agency Ghidra < 12.1.
- Is there a fix for CVE-2026-52750?
- 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-52750 attacked?
- It is attacked with local access, in a network appliance.
- Am I affected by CVE-2026-52750?
- 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
Ghidra before version 12.1 is vulnerable to a command injection flaw on Windows due to improper neutralization of shell metacharacters in URL annotations. When a user clicks a {@url ...} annotation, Ghidra invokes 'cmd.exe /c start <URL>' via Runtime.getRuntime().exec(String[]). Because Java's Windows process implementation only escapes whitespace and double quotes, cmd.exe metacharacters like '&', '|', and '^' are passed unescaped. An attacker can craft a URL containing these characters (e.g., 'http://example.com?a=b&calc.exe') to break out of the intended command and execute arbitrary code. This is a variation of the 'BatBadBut' class of vulnerabilities. The issue is fixed in Ghidra 12.1.
Affected products
- NSA Ghidra < 12.1
Timeline
- 2026-05-14: advisory: GitHub Security Advisory published by NSA developers
- 2026-06-10: disclosed: CVE published and NVD record created