# CVE-2026-54389: Ghidra < 12.1.3 PDB Parser Uncontrolled Heap Growth DoS via AbstractPdb


- **Severity:** Medium 6.7 (`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`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 20 Aug 2026
- **Updated:** 1 Oct 2026
- **Also known as:** GHSA-f75p-8cqj-9v3g

## What is CVE-2026-54389?

CVE-2026-54389 is a medium-severity vulnerability in NationalSecurityAgency ghidra, published on 20 Aug 2026. 

### Official 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.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling)

## Which versions are affected by CVE-2026-54389?


## How do I fix CVE-2026-54389?

No fix has been published for CVE-2026-54389 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-54389 being exploited?

There is no known exploitation of CVE-2026-54389 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-54389 and fix it if it is affected.

What it is: CVE-2026-54389 is a medium-severity vulnerability in NationalSecurityAgency ghidra, published on 20 Aug 2026. 
Exploitation: There is no known exploitation of CVE-2026-54389 in the wild and no public exploit code.

Affected product: NationalSecurityAgency ghidra. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-54389/ (Markdown: https://insights.sbomify.com/CVE-2026-54389/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-54389
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-54389
- OSV: https://osv.dev/vulnerability/CVE-2026-54389

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-54389/
Summaries are generated and may contain mistakes; the official description above is the record.