Is CVE-2026-6860 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-6860 being exploited in the wild.

How severe is CVE-2026-6860?

Medium severity, with a CVSS score of 5.3, published 6 May 2026.

Which products and versions are affected?

Eclipse Foundation Vert.x 4.3.4 - 4.3.8, 4.4.0 - 4.4.9, 4.5.0 - 4.5.25, 5.0.0 - 5.0.8, 4.3.4 - 4.3.8, 4.4.0 - 4.4.9, 4.5.0 - 4.5.26, 5.0.0 - 5.0.11; io.vertx:vertx-core (Maven) ECOSYSTEM:introduced=4.3.4,last_affected=4.3.8.

Is there a fix for CVE-2026-6860?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is CVE-2026-6860 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-6860?

Check whether you run Eclipse Foundation Vert.x or io.vertx:vertx-core (Maven) 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.

CVE-2026-6860: Eclipse Vert.x DoS via unbounded SNI SslContext cache growth

CVE-2026-6860 · Severity: medium · CVSS 5.3 · Published 2026-05-06

Eclipse Vert.x, a toolkit for building reactive applications on the JVM, is vulnerable to a denial-of-service attack. An unauthenticated attacker can send a large number of specially crafted connection requests that cause the server to consume excessive memory. This can eventually lead to the application crashing or becoming unresponsive, disrupting business operations.

Technologies: io.vertx:vertx-core (Maven). Vendors: Eclipse Foundation, Maven.

Quick answers

Is CVE-2026-6860 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-6860 being exploited in the wild.
How severe is CVE-2026-6860?: Medium severity, with a CVSS score of 5.3, published 6 May 2026.
Which products and versions are affected?: Eclipse Foundation Vert.x 4.3.4 - 4.3.8, 4.4.0 - 4.4.9, 4.5.0 - 4.5.25, 5.0.0 - 5.0.8, 4.3.4 - 4.3.8, 4.4.0 - 4.4.9, 4.5.0 - 4.5.26, 5.0.0 - 5.0.11; io.vertx:vertx-core (Maven) ECOSYSTEM:introduced=4.3.4,last_affected=4.3.8.
Is there a fix for CVE-2026-6860?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-6860 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-6860?: Check whether you run Eclipse Foundation Vert.x or io.vertx:vertx-core (Maven) 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.

Technical details

A resource exhaustion vulnerability exists in Vert.x TLS handling when server-side SNI is enabled with broad or wildcard hostname mappings. The vulnerability is caused by the use of `computeIfAbsent` in a cache keyed by the SNI server name, which allows an unauthenticated remote attacker to trigger unbounded cache growth by sending many distinct matching SNI names. This leads to excessive memory consumption and a potential Denial of Service (DoS). The issue affects multiple components across different versions, including SSLHelper, SslChannelProvider, and SslContextProvider. Patches are available in versions 4.5.27 and 5.0.12.

Affected products

Eclipse Vert.x 4.3.4 - 4.3.8, 4.4.0 - 4.4.9, 4.5.0 - 4.5.26, 5.0.0 - 5.0.11

Identifiers

CVE-2026-6860
GHSA-3g76-f9xq-8vp6

Timeline

2026-05-06: disclosed
2026-05-09: advisory

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.