Certificate validation bypass via case-sensitive wildcard constraints
Published Apr 8, 2026 · Updated Aug 28, 2026
Certificate validation bypass in Go crypto/x509 1.26.0-0 through 1.26.1 allows remote attackers to evade excluded DNS constraints. The dnsConstraints.query path compares wildcard DNS SANs against excluded subtrees without consistently normalizing letter case, so equivalent names can evade exclusion. Exploitation requires an otherwise trusted chain issued by a root in VerifyOptions.Roots or the system pool; acceptance can authenticate an excluded DNS identity.
Summary
What happened
Certificate validation bypass in Go crypto/x509 1.26.0-0 through 1.26.1 allows remote attackers to evade excluded DNS constraints. The dnsConstraints.query path compares wildcard DNS SANs against excluded subtrees without consistently normalizing letter case, so equivalent names can evade exclusion. Exploitation requires an otherwise trusted chain issued by a root in VerifyOptions.Roots or the system pool; acceptance can authenticate an excluded DNS identity.
The record
- CVE
- CVE-2026-33810
- Published
- Apr 8, 2026
- Updated
- Aug 28, 2026
- Vendor
- 389 Directory Server
- Product
- Assisted Installer for OpenShift Container Platform
- Classifications
- CWE-1289
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 8, 2026CVE publishedPublication date reported by the CVE source.
- Aug 28, 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?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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