Go standard library · Go · published 2026-06-02

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

Routine No exploitation evidence; EPSS 0.6%.

CVE-2026-27145 is not known to be exploited in the wild. EPSS estimates a 0.6% chance of exploitation in the next 30 days, higher than 49% of all CVEs. This Go vulnerability: CVSS 6.5 (v3.1). Fixed upstream in Go 1.26.4, 1.25.11. Routine: patch when convenient.

Share this

Remediation#

Fixed upstream in Go 1.26.4, 1.25.11.

Patch events

  1. This monthSecurity release

    Language runtimeGo

    Go security releases: 1.26.4, 1.25.11

    Upgrade to 1.26.41.25.11

    Why: Vendor security release for server software (most severe: CVE-2026-42504).

Exploit intelligence#

SignalValueSource
Known exploitedNoCISA KEV
Ransomware use—CISA KEV
EPSS (30-day exploitation probability)0.6% (49th pct)FIRST EPSS v2026.06.15
CVSS base score6.5 (v3.1)
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:H
CNA / CISA ADP
SSVC exploitationnoneCISA Vulnrichment
SSVC automatableNoCISA Vulnrichment
SSVC technical impactpartialCISA Vulnrichment

Affected versions (from the CVE record)#

Description (from the CVE record)#

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

Quoted from the CVE Program record.

Elsewhere#

Distro status: Debian · Ubuntu · Red Hat · Alpine

Something wrong on this page?
Anonymous. Reports are checked against the primary source.

Also on today's list

See today's list → · Coming up →