CVE-2026-52757

MEDIUMPre-NVD 4.44.4—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 4.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 96% 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
Elevated
4.4
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 4.4Exploit: NoneExposed: 0

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

Ghidra before 12.1 contains a heap-use-after-free vulnerability in the decompiler's HighVariable::merge() function during the variable merging pass. Attackers can trigger this vulnerability by crafting a binary that causes stale pointers in the HighIntersectTest::highedgemap cache to be dereferenced, reading and writing the flags field of freed heap memory when a user opens the binary in Ghidra's decompiler view.

CVSS v3
4.4
EG Score
4.4(medium)
EPSS
4.1%
KEV
Not listed

Published

June 10, 2026

Last Modified

July 14, 2026

Advisory Details (2)

Auto-updated Jun 15, 2026
Patch available. Sources: github.
github Patch Available

Heap-use-after-free in HighVariable::merge() during decompilation · Advisory · NationalSecurityAgency/ghidra · GitHub

https://github.com/NationalSecurityAgency/ghidra/security/advisories/GHSA-8jqp-qv73-395r
generic

Ghidra < 12.1 - Heap-use-after-free in HighVariable::merge() during decompilation | Advisories | VulnCheck

https://www.vulncheck.com/advisories/ghidra-heap-use-after-free-in-highvariable-merge-during-decompilation

Weakness Classification(1)

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

Data Freshness Timeline

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-52757?
CVE-2026-52757 is a medium vulnerability published on June 10, 2026. Ghidra before 12.1 contains a heap-use-after-free vulnerability in the decompiler's HighVariable::merge() function during the variable merging pass. Attackers can trigger this vulnerability by crafting a binary that causes stale pointers in the HighIntersectTest::highedgemap cache to be…
When was CVE-2026-52757 disclosed?
CVE-2026-52757 was first published in the National Vulnerability Database on June 10, 2026, with the most recent update on July 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-52757 actively exploited?
CVE-2026-52757 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 4.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-52757?
CVE-2026-52757 has a CVSS v3 base score of 4.4 (NVD).
How do I remediate CVE-2026-52757?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-52757, 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-52757

Explore →

Is Your Infrastructure Affected by CVE-2026-52757?

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

Start Free Scan →Browse All CVEs