# CVE-2026-113604: Ghidra 10.2 through 12.1.4 Denial of Service via ELF Loader Extended Header Counts


- **Severity:** Medium 6.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 20 Oct 2026
- **Updated:** 20 Oct 2026
- **Also known as:** GHSA-j4jr-xgjh-hpvc

## What is CVE-2026-113604?

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

### Official description

Ghidra 10.2 through 12.1.4 contains a denial of service vulnerability in the ELF loader's ElfHeader class that allocates arrays sized by unvalidated extended section and program header counts. Attackers can supply a crafted 128-byte ELF file that triggers an OutOfMemoryError during load-spec discovery at import or in headless analysis pipelines.

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

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


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

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

## Is CVE-2026-113604 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-113604 is a medium-severity vulnerability in NationalSecurityAgency ghidra, published on 20 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-113604 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-113604/ (Markdown: https://insights.sbomify.com/CVE-2026-113604/index.md)
```

## Sources

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

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