Skip to main content
VulnerabilityPublished Updated

CVE-2026-54389: NationalSecurityAgency ghidra · Unthrottled Resource Allocation

Affects NationalSecurityAgency ghidraSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.7 Medium : upgrade to 12.1.3 when convenient.

Data as of 17 Nov 2026, 20:25 UTC

CVSS 4.0 base score
6.7Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 12.1.3
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.

What to do

Upgrade NationalSecurityAgency ghidra to 12.1.3.

Affected software

ProductAffectedFixed in
NationalSecurityAgencyghidraAffected
  • <12.1.3
Fixed in–
GitHubghidrapkg:github/ghidraOther threatsAffected
  • <12.1.3
Fixed in
  • 12.1.3

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Ghidra to version 12.1.3 or later where this vulnerability is fixed. No other mitigation or workaround is indicated in the provided data.

Description

Ghidra before 12.1.3 contains an uncontrolled resource consumption vulnerability in the PDB parser that allows attackers to terminate the Ghidra process by supplying a crafted PDB file with an oversized parameters section. 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.

References

Community reviews

Loading reviews…