CVE-2026-6860
A TCP client can perform a TLS handshake and present the server name extension with a server name that is accepted by a server wildcard name, e.g. if the server is configured with a certificate accepting *.example.com, any XYZ.example.com where xyz is a valid name can be used.
Affected Software
Remediation
Patch Available
Event History
Frequently Asked Questions
What is the severity of CVE-2026-6860?
CVE-2026-6860 is considered a moderate severity vulnerability due to its potential for unbounded server name validation.
How do I fix CVE-2026-6860?
To fix CVE-2026-6860, upgrade to a patched version of io.vertx:vertx-core that is beyond the vulnerable versions mentioned.
Which versions of io.vertx:vertx-core are affected by CVE-2026-6860?
CVE-2026-6860 affects io.vertx:vertx-core versions from 4.3.4 to 5.0.8 inclusively.
What kind of attack does CVE-2026-6860 expose my server to?
CVE-2026-6860 exposes your server to potential man-in-the-middle attacks due to improper server name validation.
Is CVE-2026-6860 specific to any particular deployment?
CVE-2026-6860 specifically impacts applications utilizing wildcard certificates in their TLS configurations.