Quick answers
- Is CVE-2026-102462 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-102462 being exploited in the wild.
- How severe is CVE-2026-102462?
- Medium severity, with a CVSS score of 5.9, published 15 October 2026.
- Which products and versions are affected?
- Eclipse Vert.x MSSQL client 4.0.0 to 4.5.34, 5.0.0 to 5.0.12, 5.1.0 to 5.1.9, 5.2.0.
- Is there a fix for CVE-2026-102462?
- 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-102462 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-102462?
- Check whether you run Eclipse Vert.X or Eclipse Vert.x MSSQL client 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 TDS message decoder in vertx-mssql-client aggregates inbound protocol packets into a composite direct-memory buffer without enforcing a cumulative size limit. An attacker controlling or intercepting the SQL Server connection can send a stream of TDS packets that omit the END_OF_MESSAGE flag, causing unbounded heap allocation and an out-of-memory crash. This vulnerability exists before authentication, allowing pre-auth denial of service.
Affected products
- Eclipse Vert.x MSSQL client 4.0.0 to 4.5.34, 5.0.0 to 5.0.12, 5.1.0 to 5.1.9, 5.2.0
Timeline
- 2026-10-07: advisory
- 2026-10-15: disclosed