CVE-2026-52759

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.2%, top 95% 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.5
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.5Exploit: NoneExposed: 0

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

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.

CVSS v3
5.5
EG Score
5.5(medium)
EPSS
4.7%
KEV
Not listed

Published

June 10, 2026

Last Modified

June 11, 2026

Advisory Details (2)

Auto-updated Jun 13, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

Uncontrolled Resource Consumption in MachoLoader · Advisory · NationalSecurityAgency/ghidra · GitHub

https://github.com/NationalSecurityAgency/ghidra/security/advisories/GHSA-v6c3-h9cp-3whf
generic

Ghidra < 12.1.1 - Denial of Service via Uncontrolled Memory Allocation in Mach-O Parser | Advisories | VulnCheck

https://www.vulncheck.com/advisories/ghidra-denial-of-service-via-uncontrolled-memory-allocation-in-mach-o-parser

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 16× in last 7d / 66× 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-07-11 20:20 UTCEG score recompute
  2. 2026-07-11 08:27 UTCEPSS rescore
  3. 2026-07-11 08:27 UTCEPSS rescore
  4. 2026-07-10 18:52 UTCEG score recompute
  5. 2026-07-09 19:10 UTCEPSS rescore
  6. 2026-07-09 19:10 UTCEPSS rescore
  7. 2026-07-08 23:27 UTCEG score recompute
  8. 2026-07-08 15:16 UTCEPSS rescore
  9. 2026-07-08 15:16 UTCEPSS rescore
  10. 2026-07-07 22:03 UTCEG score recompute
  11. 2026-07-07 13:46 UTCEPSS rescore
  12. 2026-07-07 13:46 UTCEPSS rescore
  13. 2026-07-06 16:27 UTCEPSS rescore
  14. 2026-07-06 16:27 UTCEPSS rescore
  15. 2026-07-05 13:24 UTCEG score recompute
  16. 2026-07-05 02:30 UTCEPSS rescore
  17. 2026-07-04 11:54 UTCEG score recompute
  18. 2026-07-04 06:31 UTCEPSS rescore
  19. 2026-07-03 00:15 UTCEG score recompute
  20. 2026-07-01 22:50 UTCEG score recompute
  21. 2026-07-01 15:07 UTCEPSS rescore
  22. 2026-06-30 23:22 UTCEPSS rescore
  23. 2026-06-30 20:32 UTCEG score recompute
  24. 2026-06-29 18:59 UTCEG score recompute
  25. 2026-06-29 14:06 UTCEPSS rescore
Show 45 more
  1. 2026-06-29 14:06 UTCEPSS rescore
  2. 2026-06-28 17:17 UTCEG score recompute
  3. 2026-06-28 14:07 UTCEPSS rescore
  4. 2026-06-28 04:56 UTCEPSS rescore
  5. 2026-06-28 04:56 UTCEPSS rescore
  6. 2026-06-27 15:49 UTCEG score recompute
  7. 2026-06-27 03:08 UTCEPSS rescore
  8. 2026-06-26 14:23 UTCEG score recompute
  9. 2026-06-25 13:49 UTCEPSS rescore
  10. 2026-06-25 12:58 UTCEG score recompute
  11. 2026-06-24 14:05 UTCEPSS rescore
  12. 2026-06-24 11:33 UTCEG score recompute
  13. 2026-06-23 21:33 UTCEPSS rescore
  14. 2026-06-23 21:33 UTCEPSS rescore
  15. 2026-06-23 10:08 UTCEG score recompute
  16. 2026-06-22 08:43 UTCEG score recompute
  17. 2026-06-21 14:56 UTCEPSS rescore
  18. 2026-06-21 14:56 UTCEPSS rescore
  19. 2026-06-21 06:16 UTCEG score recompute
  20. 2026-06-21 01:59 UTCEPSS rescore
  21. 2026-06-21 01:59 UTCEPSS rescore
  22. 2026-06-20 04:36 UTCEG score recompute
  23. 2026-06-19 19:26 UTCEPSS rescore
  24. 2026-06-19 19:26 UTCEPSS rescore
  25. 2026-06-19 02:39 UTCEG score recompute
  26. 2026-06-18 17:52 UTCEPSS rescore
  27. 2026-06-18 17:52 UTCEPSS rescore
  28. 2026-06-18 01:14 UTCEG score recompute
  29. 2026-06-17 17:53 UTCEPSS rescore
  30. 2026-06-16 23:49 UTCEG score recompute
  31. 2026-06-16 17:53 UTCEPSS rescore
  32. 2026-06-15 22:24 UTCEG score recompute
  33. 2026-06-15 17:49 UTCEPSS rescore
  34. 2026-06-15 17:49 UTCEPSS rescore
  35. 2026-06-14 23:18 UTCEPSS rescore
  36. 2026-06-14 20:59 UTCEG score recompute
  37. 2026-06-13 23:00 UTCEPSS rescore
  38. 2026-06-13 19:35 UTCEG score recompute
  39. 2026-06-12 23:12 UTCEPSS rescore
  40. 2026-06-12 23:12 UTCEPSS rescore
  41. 2026-06-12 18:09 UTCEG score recompute
  42. 2026-06-11 16:43 UTCEG score recompute
  43. 2026-06-11 14:00 UTCEPSS rescore
  44. 2026-06-10 15:18 UTCEG score recompute
  45. 2026-06-10 15:18 UTCNVD updatefirst tracked

Frequently asked(5)

What is CVE-2026-52759?
CVE-2026-52759 is a medium vulnerability published on June 10, 2026. 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…
When was CVE-2026-52759 disclosed?
CVE-2026-52759 was first published in the National Vulnerability Database on June 10, 2026, with the most recent update on June 11, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-52759 actively exploited?
CVE-2026-52759 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 4.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-52759?
CVE-2026-52759 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-52759?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-52759, 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-52759

Explore →

Is Your Infrastructure Affected by CVE-2026-52759?

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

Start Free Scan →Browse All CVEs