Quick answers
- Is CVE-2026-102475 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-102475 being exploited in the wild.
- How severe is CVE-2026-102475?
- Medium severity, with a CVSS score of 5.9, published 15 October 2026.
- Which products and versions are affected?
- Eclipse Vert.X 5.0.0 to 5.0.12, 5.1.0 to 5.1.9, 5.2.0.
- Is there a fix for CVE-2026-102475?
- Yes: fixed in Vert.x 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-102475 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-102475?
- 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: Vert.x 5.1.10, 5.2.1
Technical details
The HTTP proxy body transformer interceptor relies on a max buffered bytes limit to prevent unbounded memory allocation, but this check is not correctly enforced. An attacker can send requests that bypass the buffering limit, causing the server to allocate heap memory indefinitely. This requires the application to use an intercepting body transformer; exploitation is over the network with no authentication or user interaction needed.
Affected products
- Eclipse Vert.x 5.0.0 to 5.0.12, 5.1.0 to 5.1.9, 5.2.0
Timeline
- 2026-10-07: disclosed: GitHub advisory published
- 2026-10-15: advisory: CVE-2026-102475 published