# Eclipse Vert.x memory leak Advisory record · `GHSA-5667-3wch-7q7w` - **Identifiers:** `GHSA-5667-3wch-7q7w` · `CVE-2024-1023` - **State:** Confirmed - **Severity:** CVSS 6.5 Medium - **Critical:** No - **Weakness (CWE):** [CWE-119](https://cwe.mitre.org/data/definitions/119.html) · [CWE-200](https://cwe.mitre.org/data/definitions/200.html) · [CWE-401](https://cwe.mitre.org/data/definitions/401.html) - **Tags:** [Memory corruption](https://agentprime.io/advisories/tag/memory-corruption.md) · [Information disclosure](https://agentprime.io/advisories/tag/info-disclosure.md) · [Denial of service](https://agentprime.io/advisories/tag/dos.md) - **Published:** 27 Mar 2024 - **Updated:** 25 Jul 2024 - **Reviewed by a person:** No Published by the GitHub Advisory Database at 27 Mar 2024, 09:30 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. ## Affected packages - `io.vertx:vertx-core` (Maven): affected `>=4.5.0, <4.5.2 || >=4.4.5, <4.4.7`; fixed in `4.5.2`, `4.4.7` ## Machine-written summary Summary written by Claude Haiku from the source advisory. Not reviewed by a person. > Eclipse Vert.x (io.vertx:vertx-core) versions 4.5.0 to before 4.5.2 and 4.4.5 to before 4.4.7 contain a memory leak in the HTTP client, caused by how it uses Netty FastThreadLocal data structures when connecting to different hosts. An attacker who can make a server built on the affected HTTP client connect to arbitrary addresses, such as by accepting attacker-supplied internet addresses, can accelerate the leak and exhaust memory. Upgrade to vertx-core 4.5.2 or 4.4.7. Written 8 Nov 2026. ## Not analysed yet We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check. ## Severity and exploitation - 6.5 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`, from CNA (redhat) - **CISA KEV:** Not listed. - **EPSS:** 0.017, the 76th percentile, on 14 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days. ## Timeline - 27 Mar 2024, 07:51 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2024-1023) - 27 Mar 2024, 08:15 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2024-1023) - 31 Oct 2026, 15:13 UTC: First seen by agentprime - 31 Oct 2026, 15:13 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-5667-3wch-7q7w) ## Sources - [GitHub Advisory Database: GHSA-5667-3wch-7q7w](https://github.com/advisories/GHSA-5667-3wch-7q7w) - [OSV: GHSA-5667-3wch-7q7w](https://osv.dev/vulnerability/GHSA-5667-3wch-7q7w) - - - - - - - - - - - - Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code. ## Check whether this affects you A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet. - With the agentprime MCP server (), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: - In a browser: reads your lockfile in the browser, never uploading it. - Whether it touches your code, with file and line: the Claude Code plugin, - As JSON: , or `POST https://api.agentprime.io/v1/match` with your packages () --- The web page: . Everything for agents: .