CVE-2026-54389 NationalSecurityAgency CVE debrief

Who should care

Ghidra users and administrators should assess exposure and prioritize remediation. The vulnerability has a medium severity and can be used to terminate the Ghidra process. Ghidra deployments should be reviewed for exposure and remediated as necessary. Security teams should verify Ghidra version and exposure.

Why it matters

CVE-2026-54389 is a medium-severity vulnerability in Ghidra that allows attackers to terminate the Ghidra process. Ghidra users and administrators should assess exposure and prioritize remediation.

• Denial of Service (DoS) via process termination
• Potential for exploitation requires verification
• Remediation priority for Ghidra deployments
• Verification of Ghidra version and exposure

Technical summary

The AbstractPdb deserialization routine reads all remaining parameters into an unbounded list, causing uncontrolled heap growth that triggers an OutOfMemoryError which bypasses exception handling and crashes the application. The vulnerability is caused by a lack of bounds checking in the deserialization routine, allowing an attacker to supply a crafted PDB file with an oversized parameters section. This can be used to terminate the Ghidra process. Ghidra users and administrators should assess exposure and prioritize remediation.

Defensive priority

Assess exposure and prioritize remediation for Ghidra deployments.

Recommended defensive actions

• Assess Ghidra deployment exposure
• Prioritize Ghidra remediation
• Verify Ghidra version
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The vulnerability is described in the CVE record and NVD detail page. Ghidra versions before 12.1.3 are affected. The AbstractPdb deserialization routine reads all remaining parameters into an unbounded list, causing uncontrolled heap growth that triggers an OutOfMemoryError which bypasses exception handling and crashes the application. The CVE record was published on 2026-08-20T22:17:21.117Z and has not been modified since then. The vulnerability allows attackers to terminate the Ghidra process by supplying a crafted PDB file with an

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.