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.
Project Subscriptions
No data.
Advisories
No advisories yet.
Fixes
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
References
History
Wed, 06 May 2026 12:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Wildcard Server Name Misuse in TLS Handshake Enables Client to Connect to Any Subdomain | |
| Weaknesses | CWE-295 |
Wed, 06 May 2026 10:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| References |
| |
| Metrics |
cvssV4_0
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: eclipse
Published:
Updated: 2026-05-06T09:55:12.531Z
Reserved: 2026-04-22T13:02:37.222Z
Link: CVE-2026-6860
No data.
Status : Received
Published: 2026-05-06T10:16:26.293
Modified: 2026-05-06T10:16:26.293
Link: CVE-2026-6860
No data.
OpenCVE Enrichment
Updated: 2026-05-06T11:45:03Z
Weaknesses