CVE-2026-54389

What it is

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.

At a glance

Exploitability

Can be exploited locally on the machine without logging in, but needs a user to act. High risk of service disruption.

Exploit odds

0.2% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2026-08-20 22:17 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-10-18 20:10 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 0.2% in the next 30 days (EPSS).
• Severity: 6.7 MEDIUM (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2026-08-20 22:17 UTC

Last modified

2026-10-18 20:10 UTC

Exploit probability

0.2% · EPSS, next 30 days

Weakness

CWE-770 · Allocation without limits

Record status

Deferred

Attack profile CVSS 4.0 · 6.7

Attack vector

Local

Complexity

Low

Attack requirements

None

Privileges needed

None

User interaction

Active

Confidentiality

None

Integrity

None

Availability

High

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2026-54389.md and follow it. Check whether this project is affected by CVE-2026-54389. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge