Bug 2466990 (CVE-2026-6860) - CVE-2026-6860 eclipse-vertx/vert.x: eclipse-vertx/vert.x: Denial of Service via TLS handshake with wildcard server name
Summary: CVE-2026-6860 eclipse-vertx/vert.x: eclipse-vertx/vert.x: Denial of Service v...
Keywords:
Status: NEW
Alias: CVE-2026-6860
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-05-06 10:02 UTC by OSIDB Bzimport
Modified: 2026-08-13 14:50 UTC (History)
92 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2026:34608 0 None None None 2026-07-02 00:05:07 UTC
Red Hat Product Errata RHSA-2026:48151 0 None None None 2026-07-29 19:53:13 UTC
Red Hat Product Errata RHSA-2026:54622 0 None None None 2026-08-13 14:50:57 UTC

Description OSIDB Bzimport 2026-05-06 10:02:06 UTC
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.

Comment 2 errata-xmlrpc 2026-07-02 00:05:02 UTC
This issue has been addressed in the following products:

  Streams for Apache Kafka 2.9.4

Via RHSA-2026:34608 https://access.redhat.com/errata/RHSA-2026:34608

Comment 3 errata-xmlrpc 2026-07-29 19:53:09 UTC
This issue has been addressed in the following products:

  Cryostat 4 on RHEL 9

Via RHSA-2026:48151 https://access.redhat.com/errata/RHSA-2026:48151

Comment 4 errata-xmlrpc 2026-08-13 14:50:52 UTC
This issue has been addressed in the following products:

  Red Hat build of Apache Camel 4.18.3 for Spring Boot 3.5.16

Via RHSA-2026:54622 https://access.redhat.com/errata/RHSA-2026:54622


Note You need to log in before you can comment on or make changes to this bug.