# CVE-2026-52759: Ghidra < 12.1.1 - Denial of Service via Uncontrolled Memory Allocation in Mach-O Parser

> Attackers can crash Ghidra by supplying a crafted Mach-O binary with an excessive load command count, causing uncontrolled memory allocation.

- **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
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 10 Jun 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-v6c3-h9cp-3whf

## What is CVE-2026-52759?

CVE-2026-52759 is a medium-severity denial of service vulnerability in Ghidra, published on 10 Jun 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Ghidra before 12.1.1 contains an uncontrolled memory allocation vulnerability in the Mach-O binary parser that allows attackers to cause denial of service. An attacker can supply a crafted Mach-O binary with an arbitrarily large ncmds load command count value, forcing the parser to allocate excessive heap memory without validating file size, crashing the Ghidra JVM.

Weakness: CWE-789 (Memory Allocation with Excessive Size Value)

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

It affects 1 product.


Products: Nsa Ghidra.

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

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

## Is CVE-2026-52759 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-52759 exists.

## Other vulnerabilities in Ghidra

- [CVE-2023-22671](https://insights.sbomify.com/CVE-2023-22671/): Command injection in n/a (critical 9.8)
- [CVE-2019-16941](https://insights.sbomify.com/CVE-2019-16941/): XML external entity in n/a (critical 9.8)
- [CVE-2019-13625](https://insights.sbomify.com/CVE-2019-13625/): XML external entity in n/a (critical 9.1)
- [CVE-2026-4946](https://insights.sbomify.com/CVE-2026-4946/): NSA Ghidra Auto-Analysis Annotation Command Execution (high 8.8)
- [CVE-2026-49498](https://insights.sbomify.com/CVE-2026-49498/): Ghidra 11.0 < 12.1 - SQL Injection in PostgreSQL Password Change via Unescaped Username (high 8.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-52759 is a medium-severity denial of service vulnerability in Ghidra, published on 10 Jun 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-52759 exists.

Affected product: 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-52759/ (Markdown: https://insights.sbomify.com/CVE-2026-52759/index.md)
```

## Sources

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

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