CVE-2026-54389

MEDIUMPre-NVD 5.55.5
EchelonGraph scoreMEDIUM confidence

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).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

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 computed
Severity55% × 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, 2026
Patch available. Sources: github_release, github.
github Patch Available

PDB Parser Resource Consumption · Advisory · NationalSecurityAgency/ghidra · GitHub

https://github.com/NationalSecurityAgency/ghidra/security/advisories/GHSA-f75p-8cqj-9v3g
github_release Patch Available

Ghidra 12.1.3

Patch available: NationalSecurityAgency/ghidra Ghidra_12.1.3_build

https://github.com/NationalSecurityAgency/ghidra/releases/tag/Ghidra_12.1.3_build

Weakness 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.

  1. 2026-08-30 01:22 UTCEPSS rescore
  2. 2026-08-29 19:50 UTCEG score recompute
  3. 2026-08-28 21:41 UTCEPSS rescore
  4. 2026-08-27 18:19 UTCEG score recompute
  5. 2026-08-27 14:25 UTCEPSS rescore
  6. 2026-08-26 17:53 UTCEG score recompute
  7. 2026-08-26 14:46 UTCEPSS rescore
  8. 2026-08-25 16:25 UTCEG score recompute
  9. 2026-08-25 15:50 UTCEG score recompute
  10. 2026-08-25 13:49 UTCEPSS rescore
  11. 2026-08-25 13:05 UTCEG score recompute
  12. 2026-08-24 12:40 UTCEG score recompute
  13. 2026-08-23 12:17 UTCEG score recompute
  14. 2026-08-23 00:19 UTCEPSS rescore
  15. 2026-08-22 11:54 UTCEG score recompute
  16. 2026-08-21 23:49 UTCEPSS rescore
  17. 2026-08-20 22:17 UTCEG score recompute
  18. 2026-08-20 22:16 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-54389?
CVE-2026-54389 is a medium vulnerability published on August 20, 2026. 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…
When was CVE-2026-54389 disclosed?
CVE-2026-54389 was first published in the National Vulnerability Database on August 20, 2026, with the most recent update on August 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-54389 actively exploited?
CVE-2026-54389 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 96.7% of all scored CVEs.
What is the CVSS score of CVE-2026-54389?
CVE-2026-54389 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-54389?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54389, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-54389

Explore →

Is Your Infrastructure Affected by CVE-2026-54389?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.