CVE-2024-1023

MEDIUMNVD 6.56.5—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.5 under NVD CVSS v3. EPSS exploit probability: 1.7%, top 26% 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
Elevated
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 2%CVSS: 6.5Exploit: Elevated riskExposed: 0

A fix is available — apply it.

A vulnerability in the Eclipse Vert.x toolkit results in a memory leak due to using Netty FastThreadLocal data structures. Specifically, when the Vert.x HTTP client establishes connections to different hosts, triggering the memory leak. The leak can be accelerated with intimate runtime knowledge, allowing an attacker to exploit this vulnerability. For instance, a server accepting arbitrary internet addresses could serve as an attack vector by connecting to these addresses, thereby accelerating the memory leak.

CVSS v3
6.5
EG Score
6.5(medium)
EG Risk
45(Track)
EG Risk 45/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
Severity65% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
2%
EPSS %ILE
75%
KEV
Not listed

Published

March 27, 2024

Last Modified

August 4, 2026

Advisory Details (10)

Auto-updated Aug 4, 2026
Patch available. Sources: redhat.
generic

Memory Leak related to io.netty.util.concurrent.FastThreadLocal in Vertx code · Issue #5078 · eclipse-vertx/vert.x · GitHub

https://github.com/eclipse-vertx/vert.x/issues/5078
redhat Patch Available

2260840 – (CVE-2024-1023) CVE-2024-1023 io.vertx/vertx-core: memory leak due to the use of Netty FastThreadLocal data structures in Vertx

https://bugzilla.redhat.com/show_bug.cgi?id=2260840
redhat Patch Available

CVE-2024-1023 - Red Hat Customer Portal

Affected: Red Hat Enterprise Linux 8 or OpenShift Container Platform 4, is affected by this vulnerability and a fix may be released to a

https://access.redhat.com/security/cve/CVE-2024-1023
redhat Patch Available
https://access.redhat.com/errata/RHSA-2024:4884
redhat Patch Available
https://access.redhat.com/errata/RHSA-2024:3989
redhat Patch Available
https://access.redhat.com/errata/RHSA-2024:3527
redhat Patch Available
https://access.redhat.com/errata/RHSA-2024:2833
redhat Patch Available
https://access.redhat.com/errata/RHSA-2024:2088
redhat Patch Available
https://access.redhat.com/errata/RHSA-2024:1706
redhat Patch Available
https://access.redhat.com/errata/RHSA-2024:1662

Vendor Advisories for CVE-2024-1023(7)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(4)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatvert.x2024-07-25redhat
redhatmta/mta-windup-addon-rhel9:6.2.3-22024-06-20redhat
redhatcryostat-tech-preview/jfr-datasource-rhel8:2.4.0-42024-04-29redhat
redhatio.vertx/vertx-core:4.4.8.redhat-000012024-04-03redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Maven(1)
PackageVulnerable rangeFixed inDependents
io.vertx:vertx-core4.4.5, 4.4.64.4.7—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 5× in last 7d / 25× 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.

Showing the most recent 100 of 186 total refreshes for this CVE.

  1. 2026-09-18 19:26 UTCEPSS rescore
  2. 2026-09-16 14:06 UTCEPSS rescore
  3. 2026-09-16 05:11 UTCEPSS rescore
  4. 2026-09-15 03:08 UTCEPSS rescore
  5. 2026-09-13 16:45 UTCEPSS rescore
  6. 2026-09-11 14:51 UTCEPSS rescore
  7. 2026-09-11 09:34 UTCEPSS rescore
  8. 2026-09-08 21:58 UTCEPSS rescore
  9. 2026-09-07 15:59 UTCEPSS rescore
  10. 2026-09-06 17:01 UTCOSV refresh
  11. 2026-09-06 13:46 UTCEPSS rescore
  12. 2026-09-05 15:26 UTCEPSS rescore
  13. 2026-09-04 13:58 UTCEPSS rescore
  14. 2026-09-04 05:04 UTCEPSS rescore
  15. 2026-09-02 14:10 UTCEPSS rescore
  16. 2026-09-01 13:52 UTCEPSS rescore
  17. 2026-08-30 19:15 UTCEPSS rescore
  18. 2026-08-30 01:20 UTCEPSS rescore
  19. 2026-08-28 21:39 UTCEPSS rescore
  20. 2026-08-27 14:23 UTCEPSS rescore
  21. 2026-08-26 14:44 UTCEPSS rescore
  22. 2026-08-25 13:47 UTCEPSS rescore
  23. 2026-08-23 00:17 UTCEPSS rescore
  24. 2026-08-21 23:47 UTCEPSS rescore
  25. 2026-08-20 22:53 UTCEPSS rescore
Show 75 more
  1. 2026-08-20 03:15 UTCOSV refresh
  2. 2026-08-19 17:02 UTCEPSS rescore
  3. 2026-08-18 13:46 UTCEPSS rescore
  4. 2026-08-17 13:45 UTCEPSS rescore
  5. 2026-08-16 14:54 UTCEPSS rescore
  6. 2026-08-16 02:12 UTCEPSS rescore
  7. 2026-08-15 01:28 UTCEPSS rescore
  8. 2026-08-13 21:58 UTCEPSS rescore
  9. 2026-08-12 13:49 UTCEPSS rescore
  10. 2026-08-11 13:40 UTCEPSS rescore
  11. 2026-08-10 23:58 UTCEPSS rescore
  12. 2026-08-09 13:45 UTCEPSS rescore
  13. 2026-08-09 13:45 UTCEPSS rescore
  14. 2026-08-08 16:35 UTCEPSS rescore
  15. 2026-08-07 16:25 UTCEPSS rescore
  16. 2026-08-06 13:45 UTCEPSS rescore
  17. 2026-08-05 19:15 UTCEPSS rescore
  18. 2026-08-04 22:33 UTCVendor advisory
  19. 2026-08-04 21:46 UTCEG score recompute
  20. 2026-08-04 21:46 UTCVendor advisory
  21. 2026-08-04 15:08 UTCEPSS rescore
  22. 2026-08-04 10:36 UTCEPSS rescore
  23. 2026-08-03 10:34 UTCEPSS rescore
  24. 2026-08-02 02:25 UTCEPSS rescore
  25. 2026-08-02 02:25 UTCEPSS rescore
  26. 2026-08-01 04:14 UTCEPSS rescore
  27. 2026-08-01 04:14 UTCEPSS rescore
  28. 2026-07-30 16:26 UTCEPSS rescore
  29. 2026-07-30 01:29 UTCEPSS rescore
  30. 2026-07-28 16:51 UTCOSV refresh
  31. 2026-07-28 15:34 UTCEPSS rescore
  32. 2026-07-27 14:11 UTCEPSS rescore
  33. 2026-07-26 14:53 UTCEPSS rescore
  34. 2026-07-26 14:53 UTCEPSS rescore
  35. 2026-07-25 14:16 UTCEPSS rescore
  36. 2026-07-24 14:16 UTCEPSS rescore
  37. 2026-07-23 14:17 UTCEPSS rescore
  38. 2026-07-23 14:17 UTCEPSS rescore
  39. 2026-07-23 02:31 UTCEG score recompute
  40. 2026-07-22 23:17 UTCEG score recompute
  41. 2026-07-22 14:07 UTCEPSS rescore
  42. 2026-07-21 15:23 UTCEPSS rescore
  43. 2026-07-20 17:06 UTCEPSS rescore
  44. 2026-07-19 14:30 UTCEPSS rescore
  45. 2026-07-19 14:30 UTCEPSS rescore
  46. 2026-07-19 02:27 UTCEPSS rescore
  47. 2026-07-18 10:03 UTCEPSS rescore
  48. 2026-07-18 10:03 UTCEPSS rescore
  49. 2026-07-15 16:56 UTCEPSS rescore
  50. 2026-07-15 16:56 UTCEPSS rescore
  51. 2026-07-15 01:59 UTCEPSS rescore
  52. 2026-07-15 01:59 UTCEPSS rescore
  53. 2026-07-13 22:28 UTCEPSS rescore
  54. 2026-07-12 05:45 UTCEPSS rescore
  55. 2026-07-12 05:45 UTCEPSS rescore
  56. 2026-07-11 08:52 UTCOSV refresh
  57. 2026-07-11 08:26 UTCEPSS rescore
  58. 2026-07-09 19:09 UTCEPSS rescore
  59. 2026-07-08 15:13 UTCEPSS rescore
  60. 2026-07-07 13:45 UTCEPSS rescore
  61. 2026-07-07 13:45 UTCEPSS rescore
  62. 2026-07-06 16:26 UTCEPSS rescore
  63. 2026-07-06 02:22 UTCEPSS rescore
  64. 2026-07-06 02:22 UTCEPSS rescore
  65. 2026-07-05 02:29 UTCEPSS rescore
  66. 2026-07-04 06:30 UTCEPSS rescore
  67. 2026-07-04 06:30 UTCEPSS rescore
  68. 2026-07-01 15:05 UTCEPSS rescore
  69. 2026-06-30 23:21 UTCEPSS rescore
  70. 2026-06-30 23:21 UTCEPSS rescore
  71. 2026-06-29 14:05 UTCEPSS rescore
  72. 2026-06-28 14:06 UTCEPSS rescore
  73. 2026-06-28 14:06 UTCEPSS rescore
  74. 2026-06-28 04:55 UTCEPSS rescore
  75. 2026-06-27 03:07 UTCEPSS rescore

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2024-1023?
CVE-2024-1023 is a medium vulnerability published on March 27, 2024. A vulnerability in the Eclipse Vert.x toolkit results in a memory leak due to using Netty FastThreadLocal data structures. Specifically, when the Vert.x HTTP client establishes connections to different hosts, triggering the memory leak. The leak can be accelerated with intimate runtime knowledge,…
When was CVE-2024-1023 disclosed?
CVE-2024-1023 was first published in the National Vulnerability Database on March 27, 2024, with the most recent update on August 4, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-1023 actively exploited?
CVE-2024-1023 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2% probability of exploitation in the next 30 days, which ranks it in the top 24.5% of all scored CVEs.
What is the CVSS score of CVE-2024-1023?
CVE-2024-1023 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2024-1023?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-1023, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-1023

Explore →

Is Your Infrastructure Affected by CVE-2024-1023?

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

Start Free Scan →Browse All CVEs