JVM crash via cyclic Mach-O export trie
Published Jun 10, 2026 · Updated Jun 10, 2026
Uncontrolled resource consumption in Ghidra 10.2 through 12.0.4 allows context-dependent attackers to crash the JVM with a crafted Mach-O file. ExportTrie.parseTrie() repeatedly queues previously visited offsets and concatenates node names because its breadth-first traversal has no cycle detection or resource bound. Exploitation requires an analyst to import the file; the uncaught OutOfMemoryError ends GUI or headless processing and destroys unsaved work.
Summary
What happened
Uncontrolled resource consumption in Ghidra 10.2 through 12.0.4 allows context-dependent attackers to crash the JVM with a crafted Mach-O file. ExportTrie.parseTrie() repeatedly queues previously visited offsets and concatenates node names because its breadth-first traversal has no cycle detection or resource bound. Exploitation requires an analyst to import the file; the uncaught OutOfMemoryError ends GUI or headless processing and destroys unsaved work.
The record
- CVE
- CVE-2026-49495
- Published
- Jun 10, 2026
- Updated
- Jun 10, 2026
- Vendor
- National Security Agency
- Product
- Ghidra
- Classifications
- CWE-770, T1204.002, T1499.004
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 10, 2026CVE publishedPublication date reported by the CVE source.
- Jun 10, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=10.2 <12.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Mach-O export-trie circular-reference proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo