CVE-2026-18718

CVE-2026-18718 is a supply chain vulnerability in Ghidra's SwiftNativeDemangler that executes arbitrary code when a shared project is opened. The demangler resolves a persisted tool path from project state and executes it with Ghidra's full privileges — no scripts, no macros, no user prompts. This fundamentally inverts Ghidra's threat model: you've always treated project files as inert state, but they can now carry attacker-controlled execution paths. The privilege escalation dimension is critical. Ghidra routinely runs as root when analyzing kernel extensions, drivers, or system-level malware. Opening a malicious project in an elevated session gives the attacker root-level code execution without exploiting anything — the vulnerability inherits whatever privileges Ghidra holds. If you're analyzing kernel malware in a root Ghidra session, this CVE transforms a shared project file into a privilege escalation vector. The demangler occupies a specific blind spot in analyst mental models: demanglers are perceived as passive string transformers, the software equivalent of syntax highlighters. Nobody audits demanglers, nobody sandboxes them in threat models. The vulnerability exploits exactly that gap — a component that looks safe but contains path resolution logic capable of executing binaries. The NSA built a binary executor inside a tool category whose users categorically do not expect execution. Here's what you should do now: 1. Audit your shared Ghidra project repositories for any `.gpr` files that may have been shared before this disclosure. The malicious path lives in project state — patching Ghidra doesn't purge old projects of the trigger. 2. If you use the Swift demangler, verify what tool path is persisted in your existing projects. Look for any non-standard directory references in the project configuration. 3. Treat Ghidra projects the same way you treat executable attachments from untrusted sources. Assume project state can contain execution paths, and consider whether your shared project workflows need integrity verification. 4. For incident responders: the project file itself is the exploit payload. The malicious binary may no longer exist on disk, but the project contains everything needed to reconstruct the attacker's intent. The CVSS 7.0 rating obscures the real danger. This is a silent, zero-interaction, project-file-mediated execution path — precisely the class that propagates through analyst collaboration pipelines and threat intel exchanges. The network effect of a community that treats project exchange as routine workflow is the actual blast radius. A single project dropped in a shared repo can sit dormant for months or years before someone opens it and triggers execution. This isn't a bounded RCE — it's a supply chain exploit with an arbitrarily long detection window.

Reviewed through automated stages and approved by a human before publication.