Quick answers
- Is CVE-2026-102479 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-102479 being exploited in the wild.
- How severe is CVE-2026-102479?
- Informational severity, published 14 October 2026.
- Which products and versions are affected?
- Eclipse Vert.X 5.0.0 through 5.0.12, 5.1.0 through 5.1.9, 5.2.0.
- Is there a fix for CVE-2026-102479?
- Yes: fixed in 5.0.13, 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-102479 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-102479?
- 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: 5.0.13, 5.1.10, 5.2.1
Technical details
The Vert.x HTTP/1.x decoder uses header canonicalization that allows well-crafted headers to be misinterpreted as standard HTTP headers, enabling request smuggling attacks. The vulnerability affects vertx-core, requires only network access with no authentication or user interaction, and allows an attacker to manipulate request processing logic. A fix is available in patched versions.
Affected products
- Eclipse Vert.x 5.0.0 through 5.0.12, 5.1.0 through 5.1.9, 5.2.0
Timeline
- 2026-10-07: disclosed
- 2026-10-14: advisory