CVE-2026-27145
Inefficient candidate hostname parsing in crypto/x509
CVE-2026-27145 affects Go standard library crypto/x509 (CVSS 6.5, Medium).
No known exploitation. EPSS puts it in the 49th percentile. Fixed versions are out.
No public exploit knownFix1 product2 fixed builds listed below
e.g. OID 1.3.6.1.4.1.25623.1.1.10.2026.0276
What to do
Find your product and version, then upgrade to the build on the right.
- Go standard library crypto/x509Affected: < 1.25.11Upgrade to: 1.25.11Affected: ≥ 1.26.0-0, < 1.26.4Upgrade to: 1.26.4Stated by: CVE record
Versions as the sources state them. Full version matrix after sign-in
What it is
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.
In plain language
No plain-language summary for this CVE yet.
Exploitation
Where each signal puts this CVE on the scale from published to confirmed exploited.
- CISA KEV
Not in the catalog. CISA has not confirmed exploitation.
- Public exploits
No public exploit or proof of concept found in the sources we track.
- EPSS
0.6% chance of exploitation activity in the next 30 days, which ranks it in the 49th percentile of scored CVEs.
Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.
Lifecycle
48 events over 108 days, from the signal feeds we watch.
- Record updated
- Record updated
- Record updated
- Record updated
- Record updated
- Record updated
Affected products
Technical detail
CVSS 3.1 vector
Open in the CVSS calculatorCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:H
Scored 6.5 by NVD.
How it is reached
- Attack Vector NetworkExploitable remotely over the network without any special conditions
- Attack Complexity HighRequires specific conditions like a race condition or non-default configuration
- Privileges Required NoneNo authentication required — anyone can exploit this
- User Interaction NoneNo user interaction needed — fully automated exploitation
Scope
- Scope UnchangedImpact is limited to the vulnerable component itself
Impact if exploited
- Confidentiality NoneNo confidentiality impact
- Integrity LowData modification is possible but limited in scope or consequence
- Availability HighTotal denial of service — the component is completely unavailable
Weaknesses
Sources
References in the record
And 97 more references. See all after sign-in
Questions about CVE-2026-27145
- Is CVE-2026-27145 being exploited?
- No exploitation is confirmed and no public exploit is known. EPSS puts the chance of exploitation in the next 30 days at 0.6%.
- Which versions are affected by CVE-2026-27145?
- Crypto/x509: < 1.25.11; ≥ 1.26.0-0, < 1.26.4.
- How do I fix or mitigate CVE-2026-27145?
- Upgrade to a fixed build for your product branch: 1.25.11, 1.26.4.
Last updated
Watch the software you run.
My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.
We'll flag the next CVE, public exploit or patch for Crypto/x509, not every advisory.
A free account adds
- The full version matrix and every affected product
- Exploit links, proofs of concept and Metasploit modules
- Email alerts for the products you watch
- The same data over REST API, MCP and CLI