crypto-x509 up to 1.25.10/1.26.3 on Go VerifyHostname algorithmic complexity
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.6 | $0-$5k | 0.00 |
Summary
A vulnerability labeled as problematic has been found in crypto-x509 up to 1.25.10/1.26.3 on Go. This issue affects the function VerifyHostname. Such manipulation leads to algorithmic complexity.
This vulnerability is uniquely identified as CVE-2026-27145. The attack can be launched remotely. No exploit exists.
The affected component should be upgraded.
Details
A vulnerability was found in crypto-x509 up to 1.25.10/1.26.3 on Go and classified as problematic. Affected by this issue is the function VerifyHostname. The manipulation with an unknown input leads to a algorithmic complexity vulnerability. Using CWE to declare the problem leads to CWE-407. An algorithm in a product has an inefficient worst-case computational complexity that may be detrimental to system performance and can be triggered by an attacker, typically using crafted manipulations that ensure that the worst case is being reached. Impacted is availability. CVE summarizes:
(*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.
This vulnerability is handled as CVE-2026-27145 since 02/17/2026. The exploitation is known to be difficult. The attack may be launched remotely. No form of authentication is required for exploitation. Technical details are known, but there is no available exploit. This vulnerability is assigned to T1499 by the MITRE ATT&CK project.
Upgrading to version 1.25.11 or 1.26.4 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at CERT Bund (WID-SEC-2026-1776). If you want to get best quality of vulnerability data, you may have to visit VulDB.
Affected
- Golang Go
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.7VulDB Meta Temp Score: 3.6
VulDB Base Score: 3.7
VulDB Temp Score: 3.6
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Algorithmic complexityCWE: CWE-407 / CWE-404
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: crypto-x509 1.25.11/1.26.4
Timeline
02/17/2026 CVE reserved06/02/2026 VulDB entry created
06/03/2026 Advisory disclosed
06/04/2026 VulDB entry last update
Sources
Status: ConfirmedCVE: CVE-2026-27145 (🔒)
GCVE (CVE): GCVE-0-2026-27145
GCVE (VulDB): GCVE-100-368042
CERT Bund: WID-SEC-2026-1776 - Golang Go: Mehrere Schwachstellen
Entry
Created: 06/03/2026 01:36Updated: 06/04/2026 09:48
Changes: 06/03/2026 01:36 (53), 06/04/2026 09:48 (7)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.