CVE-2026-33810: Case-sensitive excludedSubtrees name constraints cause Auth Bypass in crypto/x509
When verifying a certificate chain containing excluded DNS constraints, these constraints are not correctly applied to wildcard DNS SANs which use a different case than the constraint. This only affects validation of otherwise trusted certificate chains, issued by a root CA in the VerifyOptions.Roots CertPool, or in the system certificate pool.
Security readout for executives and security teams
Some Go certificate validation can wrongly accept a trusted certificate chain when DNS name constraints exclude a domain but a wildcard DNS name uses different letter casing. This can weaken certificate-based trust boundaries, especially in environments using private PKI, constrained certificate authorities, mTLS, or custom trust pools. Exposure is most likely in Go applications or services that validate certificates using crypto/x509 and trust roots from a system pool or configured CertPool. Risk is higher where name-constrained subordinate CAs, private PKI, custom roots, or mTLS authorization boundaries are important. Treat as high priority for Go-based systems relying on certificate validation for access control or service identity. Patch planning should focus on internet-facing services, mTLS-heavy platforms, and environments using private or constrained CAs. Mitigation focus: Check Go advisory GO-2026-4866 and vendor guidance for fixed versions.; Apply Go toolchain, runtime, container, and OS vendor updates when available.; Inventory Go services that perform TLS, mTLS, or certificate chain validation..
Prepared
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-1289: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-1289 · source CWE mapping
Improper Validation of Unsafe Equivalence in Input
Improper Validation of Unsafe Equivalence in Input represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Improper Certificate Validation represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.