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.
CVE-2026-54389
This medium-severity CVE scores 5.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 97% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.5
- EG Score
- 5.5(medium)
- EG Risk
- 25(Track)EG Risk 25/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity55% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 3%
- KEV
- Not listed
Published
August 20, 2026
Last Modified
August 25, 2026
Advisory Details (2)
Auto-updated Aug 20, 2026PDB Parser Resource Consumption · Advisory · NationalSecurityAgency/ghidra · GitHub
https://github.com/NationalSecurityAgency/ghidra/security/advisories/GHSA-f75p-8cqj-9v3gGhidra 12.1.3
Patch available: NationalSecurityAgency/ghidra Ghidra_12.1.3_build
https://github.com/NationalSecurityAgency/ghidra/releases/tag/Ghidra_12.1.3_buildWeakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 13× in last 7d / 18× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-29 19:50 UTCEG score recompute
- 2026-08-28 21:41 UTCEPSS rescore
- 2026-08-27 18:19 UTCEG score recompute
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-26 17:53 UTCEG score recompute
- 2026-08-26 14:46 UTCEPSS rescore
- 2026-08-25 16:25 UTCEG score recompute
- 2026-08-25 15:50 UTCEG score recompute
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-25 13:05 UTCEG score recompute
- 2026-08-24 12:40 UTCEG score recompute
- 2026-08-23 12:17 UTCEG score recompute
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-22 11:54 UTCEG score recompute
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-20 22:17 UTCEG score recompute
- 2026-08-20 22:16 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-770
Frequently asked(5)
What is CVE-2026-54389?
When was CVE-2026-54389 disclosed?
Is CVE-2026-54389 actively exploited?
What is the CVSS score of CVE-2026-54389?
How do I remediate CVE-2026-54389?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-54389
Is Your Infrastructure Affected by CVE-2026-54389?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.