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.
Fix
Patch, vendor advisory and mitigation references on NVD 2
- https://github.com/eclipse-vertx/vert.x/pull/6102 Issue Tracking, Patch
- https://github.com/eclipse-vertx/vert.x/security/advisories/GHSA-3g76-f9xq-8vp6 Exploit, Vendor Advisory
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 6.9 · eclipseNVD modified 2026-10-26 19:10
Affected (CPE criteria) 1
cpe:2.3:a:eclipse:vert.x:*:*:*:*:*:*:*:*
References 4
- https://github.com/eclipse-vertx/vert.x/pull/6102 Issue Tracking, Patch
- https://github.com/eclipse-vertx/vert.x/security/advisories/GHSA-3g76-f9xq-8vp6 Exploit, Vendor Advisory
- https://gitlab.eclipse.org/security/vulnerability-reports/-/issues/381 Exploit, Issue Tracking, Third Party Advisory
- https://gitlab.eclipse.org/security/vulnerability-reports/-/issues/381 Exploit, Issue Tracking, Third Party Advisory