Quick answers
- Is CVE-2026-102467 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-102467 being exploited in the wild.
- How severe is CVE-2026-102467?
- Medium severity, with a CVSS score of 5.9, published 15 October 2026.
- Which products and versions are affected?
- Eclipse Vert.X 4.0.0–4.5.34, 5.0.0–5.0.12, 5.1.0–5.1.9, 5.2.0.
- Is there a fix for CVE-2026-102467?
- Yes: fixed in 4.5.35, 5.1.10, 5.2.1. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-102467 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-102467?
- Check whether you run Eclipse Vert.X at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 4.5.35, 5.1.10, 5.2.1
Technical details
The WebSocket implementation in vertx-core does not define a maximum allocation limit when decompressing frames or messages, enabling zip bomb attacks that exhaust server memory. The vulnerability affects versions 4.0.0–4.5.34, 5.0.0–5.0.12, 5.1.0–5.1.9, and 5.2.0. An unauthenticated network attacker can trigger the denial of service with a single malicious WebSocket connection.
Affected products
- Eclipse Vert.x 4.0.0–4.5.34, 5.0.0–5.0.12, 5.1.0–5.1.9, 5.2.0
Timeline
- 2026-10-07: disclosed
- 2026-10-15: advisory