CVE-2024-53018

MEDIUMNVD 6.66.6—
EchelonGraph scoreMEDIUM confidence

Score 6.6 from GitHub Security Advisory published 2025-06-03. NVD baseline CVSS 6.6; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
6.6
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 6.6Exploit: NoneExposed: 0

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

Memory corruption may occur while processing the OIS packet parser.

CVSS v3
6.6
EG Score
6.6(medium)
EG Risk
30(Track)
EG Risk 30/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity66% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
0.0%
KEV
Not listed

Published

June 3, 2025

Last Modified

August 20, 2025

References (1)

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 1× in last 7d / 10× 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-23 02:43 UTCEG score recompute
  2. 2026-07-15 01:59 UTCEPSS rescore
  3. 2026-07-15 01:59 UTCEPSS rescore
  4. 2026-07-13 22:29 UTCEPSS rescore
  5. 2026-07-08 15:14 UTCEPSS rescore
  6. 2026-07-07 13:45 UTCEPSS rescore
  7. 2026-06-28 04:55 UTCEPSS rescore
  8. 2026-06-28 04:55 UTCEPSS rescore
  9. 2026-06-23 21:32 UTCEPSS rescore
  10. 2026-06-23 21:32 UTCEPSS rescore
  11. 2026-06-15 17:47 UTCEPSS rescore
  12. 2026-06-14 23:17 UTCEPSS rescore
  13. 2026-06-13 22:59 UTCEPSS rescore
  14. 2026-06-13 22:59 UTCEPSS rescore
  15. 2026-06-13 22:59 UTCEPSS rescore
  16. 2026-06-12 23:11 UTCEPSS rescore
  17. 2026-06-12 23:11 UTCEPSS rescore
  18. 2026-06-11 13:59 UTCEPSS rescore
  19. 2026-06-10 22:18 UTCEPSS rescore
  20. 2026-06-10 13:21 UTCEPSS rescore
  21. 2026-06-08 14:16 UTCEPSS rescore
  22. 2026-06-08 14:16 UTCEPSS rescore
  23. 2026-06-07 15:24 UTCEPSS rescore
  24. 2026-06-07 15:24 UTCEPSS rescore
  25. 2026-06-06 13:46 UTCEPSS rescore
Show 16 more
  1. 2026-06-06 13:46 UTCEPSS rescore
  2. 2026-06-05 22:46 UTCEPSS rescore
  3. 2026-06-05 22:46 UTCEPSS rescore
  4. 2026-06-05 06:09 UTCEPSS rescore
  5. 2026-06-05 06:09 UTCEPSS rescore
  6. 2026-06-04 13:11 UTCEPSS rescore
  7. 2026-06-04 13:11 UTCEPSS rescore
  8. 2026-06-01 13:51 UTCEPSS rescore
  9. 2026-06-01 13:51 UTCEPSS rescore
  10. 2026-05-31 22:30 UTCEPSS rescore
  11. 2026-05-31 22:30 UTCEPSS rescore
  12. 2026-05-31 00:16 UTCEPSS rescore
  13. 2026-05-31 00:16 UTCEPSS rescore
  14. 2026-05-30 04:22 UTCEG score recompute
  15. 2026-05-30 04:22 UTCGHSA enrichment
  16. 2026-05-29 13:43 UTCEPSS rescore

Frequently asked(5)

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

Explore →

Is Your Infrastructure Affected by CVE-2024-53018?

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

Start Free Scan →Browse All CVEs