CVE-2026-52753

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.0.3 contains an out-of-memory vulnerability in the rust_demangle function that allocates unbounded output buffers without size limits. Attackers can craft malicious Rust symbol names in binaries to trigger exponential memory allocation, causing process crashes during binary analysis.

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 16, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

Out-of-Memory in Ghidra GNU Demangler causes Process Crash · Advisory · NationalSecurityAgency/ghidra · GitHub

https://github.com/NationalSecurityAgency/ghidra/security/advisories/GHSA-m94m-fqr3-x442
generic

Ghidra < 12.0.3 - Out-of-Memory in Rust Symbol Demangler via Malformed Symbol | Advisories | VulnCheck

https://www.vulncheck.com/advisories/ghidra-out-of-memory-in-rust-symbol-demangler-via-malformed-symbol

Weakness Classification(1)

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

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2026-52753?
CVE-2026-52753 is a medium vulnerability published on June 10, 2026. Ghidra before 12.0.3 contains an out-of-memory vulnerability in the rust_demangle function that allocates unbounded output buffers without size limits. Attackers can craft malicious Rust symbol names in binaries to trigger exponential memory allocation, causing process crashes during binary…
When was CVE-2026-52753 disclosed?
CVE-2026-52753 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-52753 actively exploited?
CVE-2026-52753 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-52753?
CVE-2026-52753 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-52753?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-52753, 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-52753

Explore →

Is Your Infrastructure Affected by CVE-2026-52753?

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

Start Free Scan →Browse All CVEs