Metrics
Affected Vendors & Products
No advisories yet.
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
Thu, 13 Aug 2026 13:30:00 +0000
Wed, 12 Aug 2026 12:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| References |
|
Wed, 12 Aug 2026 02:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-400 |
Tue, 11 Aug 2026 16:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| References |
|
Thu, 04 Jun 2026 14:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
cvssV3_1
|
Wed, 03 Jun 2026 04:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Go Standard Library
Go Standard Library crypto/x509 |
|
| Weaknesses | CWE-400 | |
| Vendors & Products |
Go Standard Library
Go Standard Library crypto/x509 |
Wed, 03 Jun 2026 02:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | (*x509.Certificate).VerifyHostname previously called matchHostnames in a loop over all DNS Subject Alternative Name (SAN) entries. This caused strings.Split(host, ".") to execute repeatedly on the same input hostname. With a large DNS SAN list, verification costs scaled quadratically based on the number of SAN entries multiplied by the hostname's label count. Because x509.Verify validates hostnames before building the certificate chain, this overhead occurred even for untrusted certificates. | |
| Title | Inefficient candidate hostname parsing in crypto/x509 | |
| References |
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: Go
Published:
Updated: 2026-08-13T12:04:36.690Z
Reserved: 2026-02-17T19:57:28.435Z
Link: CVE-2026-27145
Updated: 2026-08-13T12:04:36.690Z
Status : Awaiting Analysis
Published: 2026-06-02T23:16:35.570
Modified: 2026-08-13T13:18:09.840
Link: CVE-2026-27145
No data.
OpenCVE Enrichment
Updated: 2026-08-13T23:00:06Z