Remote service hang via repeated hostname splitting
Published Jun 2, 2026 · Updated Aug 27, 2026
CPU exhaustion in Go standard library crypto/x509 before 1.25.11 and 1.26.0 through 1.26.3 allows remote attackers to hang services. VerifyHostname calls matchHostnames for every DNS SAN and repeatedly splits the same candidate hostname, making work scale with SAN entries and labels. An untrusted certificate is sufficient because hostname validation precedes chain building; the bounded consequence is CPU-driven service unresponsiveness.
Summary
What happened
CPU exhaustion in Go standard library crypto/x509 before 1.25.11 and 1.26.0 through 1.26.3 allows remote attackers to hang services. VerifyHostname calls matchHostnames for every DNS SAN and repeatedly splits the same candidate hostname, making work scale with SAN entries and labels. An untrusted certificate is sufficient because hostname validation precedes chain building; the bounded consequence is CPU-driven service unresponsiveness.
The record
- CVE
- CVE-2026-27145
- Published
- Jun 2, 2026
- Updated
- Aug 27, 2026
- Vendor
- 389 Directory Server
- Product
- Assisted Installer for OpenShift Container Platform
- Classifications
- CWE-606, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 2, 2026CVE publishedPublication date reported by the CVE source.
- Aug 27, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo