CVE-2026-27145: Inefficient candidate hostname parsing in crypto/x509

Published Jun 2, 2026
·
Updated

(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.

Other sources

Inefficient candidate hostname parsing in crypto/x509

— Microsoft

Affected Software

4 affected componentsFixes available
go crypto/x509
go/stdlib<1.25.11
1.25.11
go/stdlib>=1.26.0-0<1.26.4
1.26.4
IBM API Connect<=V10.0.8.0 - V10.0.8.13

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade go/stdlib to a version that resolves this vulnerability.

    Fixed in 1.25.11
  2. Upgrade

    Upgrade go/stdlib to a version that resolves this vulnerability.

    Fixed in 1.26.4

Event History

Jun 2, 2026
Advisory Published
via OSV·09:39 PM
Data Sourced
via OSV·09:39 PM
DescriptionAffected Software
CVE Published
via MITRE·10:01 PM
Data Sourced
via MITRE·10:01 PM
DescriptionWeakness
Data Sourced
via Red Hat·11:01 PM
DescriptionSeverityAffected Software
Data Sourced
via NVD·11:16 PM
DescriptionSeverityWeakness
Jun 3, 2026
Exploit Published
via GitHub·02:21 AM
Jun 6, 2026
Data Sourced
via Microsoft·08:01 AM
DescriptionSeverityWeakness
Nov 18, 2026
Data Sourced
via IBM·12:00 AM
DescriptionAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Frequently Asked Questions

1

What is the severity of CVE-2026-27145?

CVE-2026-27145 has a medium severity rating of 6.5 according to the CVSS 3.1 scoring system.

2

How does CVE-2026-27145 affect hostname verification?

CVE-2026-27145 causes inefficient hostname verification due to the repeated execution of string.Split on the input hostname for large DNS Subject Alternative Name (SAN) entries.

3

What are the consequences of CVE-2026-27145?

The consequences of CVE-2026-27145 include potentially significant performance degradation during hostname verification with large SAN lists.

4

How can CVE-2026-27145 be mitigated?

Mitigation of CVE-2026-27145 can be achieved by updating to the latest version of the go/crypto/x509 library that addresses the inefficient hostname parsing.

5

When was CVE-2026-27145 published?

CVE-2026-27145 was published on June 2, 2026.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203