CVE-2024-58350

MEDIUMNVD 4.04.0
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 4.0 under NVD CVSS v3. EPSS exploit probability: 0.1%, top 98% 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, nvd
4.0
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 4.0Exploit: NoneExposed: 0

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

Ghidra before 11.2 contains a use after free vulnerability in the Sleigh backend caused by undefined static initialization order of the SleighArchitecture::translators and XmlArchitectureCapability singletons. Attackers can trigger an infinite loop or denial of service during shutdown by exploiting the unsafe destruction order that causes iteration over deallocated memory.

CVSS v3
4.0
EG Score
4.0(medium)
EPSS
1.5%
KEV
Not listed

Published

June 10, 2026

Last Modified

July 14, 2026

Advisory Details (2)

Auto-updated Jun 19, 2026
Patch available. Sources: github.
generic

Ghidra < 11.2 - Use After Free in Sleigh Backend via Static Initialization Order | Advisories | VulnCheck

https://www.vulncheck.com/advisories/ghidra-use-after-free-in-sleigh-backend-via-static-initialization-order
github Patch Available

Use after free vulnerability in Sleigh backend · Advisory · NationalSecurityAgency/ghidra · GitHub

https://github.com/NationalSecurityAgency/ghidra/security/advisories/GHSA-4g43-2f29-xvp4

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 36× 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-22 14:07 UTCEPSS rescore
  2. 2026-07-21 15:23 UTCEPSS rescore
  3. 2026-07-20 17:07 UTCEPSS rescore
  4. 2026-07-19 14:30 UTCEPSS rescore
  5. 2026-07-19 14:30 UTCEPSS rescore
  6. 2026-07-18 10:03 UTCEPSS rescore
  7. 2026-07-16 17:02 UTCEPSS rescore
  8. 2026-07-15 16:57 UTCEPSS rescore
  9. 2026-07-15 01:59 UTCEPSS rescore
  10. 2026-07-15 01:59 UTCEPSS rescore
  11. 2026-07-14 23:23 UTCNVD updateCVSS v3 → 4 · severity → MEDIUM
  12. 2026-07-14 23:10 UTCMITRE cvelistV5CVSS v3 → 2.9 · severity → LOW
  13. 2026-07-13 22:29 UTCEPSS rescore
  14. 2026-07-09 19:09 UTCEPSS rescore
  15. 2026-07-09 19:09 UTCEPSS rescore
  16. 2026-07-08 15:14 UTCEPSS rescore
  17. 2026-07-07 13:45 UTCEPSS rescore
  18. 2026-07-07 13:45 UTCEPSS rescore
  19. 2026-07-06 16:26 UTCEPSS rescore
  20. 2026-07-06 16:26 UTCEPSS rescore
  21. 2026-07-05 02:29 UTCEPSS rescore
  22. 2026-07-04 06:30 UTCEPSS rescore
  23. 2026-07-04 06:30 UTCEPSS rescore
  24. 2026-07-01 15:06 UTCEPSS rescore
  25. 2026-06-30 23:21 UTCEPSS rescore
Show 32 more
  1. 2026-06-30 23:21 UTCEPSS rescore
  2. 2026-06-28 14:07 UTCEPSS rescore
  3. 2026-06-28 04:55 UTCEPSS rescore
  4. 2026-06-28 04:55 UTCEPSS rescore
  5. 2026-06-27 03:08 UTCEPSS rescore
  6. 2026-06-27 03:07 UTCEPSS rescore
  7. 2026-06-25 13:49 UTCEPSS rescore
  8. 2026-06-25 13:49 UTCEPSS rescore
  9. 2026-06-24 14:04 UTCEPSS rescore
  10. 2026-06-24 14:04 UTCEPSS rescore
  11. 2026-06-23 21:32 UTCEPSS rescore
  12. 2026-06-21 14:56 UTCEPSS rescore
  13. 2026-06-21 14:56 UTCEPSS rescore
  14. 2026-06-21 01:59 UTCEPSS rescore
  15. 2026-06-19 19:25 UTCEPSS rescore
  16. 2026-06-19 19:25 UTCEPSS rescore
  17. 2026-06-18 17:52 UTCEPSS rescore
  18. 2026-06-18 17:52 UTCEPSS rescore
  19. 2026-06-17 17:52 UTCEPSS rescore
  20. 2026-06-16 17:52 UTCEPSS rescore
  21. 2026-06-15 17:48 UTCEPSS rescore
  22. 2026-06-14 23:17 UTCEPSS rescore
  23. 2026-06-13 22:59 UTCEPSS rescore
  24. 2026-06-13 22:59 UTCEPSS rescore
  25. 2026-06-13 11:53 UTCEG score recompute 1.10
  26. 2026-06-12 23:11 UTCEPSS rescore
  27. 2026-06-12 23:11 UTCEPSS rescore
  28. 2026-06-11 19:56 UTCNVD updateCVSS v3 → 4 · severity → MEDIUM
  29. 2026-06-11 13:59 UTCEPSS rescore
  30. 2026-06-11 13:59 UTCEPSS rescore
  31. 2026-06-10 15:19 UTCEG score recompute
  32. 2026-06-10 15:18 UTCNVD updatefirst tracked

Frequently asked(5)

What is CVE-2024-58350?
CVE-2024-58350 is a medium vulnerability published on June 10, 2026. Ghidra before 11.2 contains a use after free vulnerability in the Sleigh backend caused by undefined static initialization order of the SleighArchitecture::translators and XmlArchitectureCapability singletons. Attackers can trigger an infinite loop or denial of service during shutdown by exploiting…
When was CVE-2024-58350 disclosed?
CVE-2024-58350 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-2024-58350 actively exploited?
CVE-2024-58350 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2024-58350?
CVE-2024-58350 has a CVSS v3 base score of 4.0 (NVD).
How do I remediate CVE-2024-58350?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-58350, 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-2024-58350

Explore →

Is Your Infrastructure Affected by CVE-2024-58350?

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