CVE-2026-33810: 
Go vulnerability analysis and mitigation

CVE-2026-33810 is a certificate chain validation bypass vulnerability in the Go standard library's crypto/x509 module, classified as Improper Certificate Validation (CWE-295). When verifying a certificate chain containing excluded DNS name constraints, the constraints are not correctly applied to wildcard DNS Subject Alternative Names (SANs) that use a different letter case than the constraint — for example, a constraint for example.com would fail to block a wildcard SAN of *.EXAMPLE.COM. The vulnerability affects Go versions 1.26.0 through 1.26.1 (fixed in 1.26.2) and only impacts validation of certificate chains issued by a trusted root CA in VerifyOptions.Roots or the system certificate pool. It was published on April 8, 2026, with a CVSS v3.1 base score of 8.2 (High) per Feedly/NVD data, though the GitHub Advisory Database scores it 7.5 (High) (GitHub Advisory, Go Advisory).

The root cause is a case-sensitivity flaw in the crypto/x509 certificate chain verification logic (CWE-295). When the library evaluates excluded DNS name constraints (defined in X.509 name constraints extensions), it performs a case-sensitive comparison against wildcard DNS SANs, meaning a constraint like excluded: example.com would not match a SAN of *.EXAMPLE.COM or *.Example.Com. RFC 5280 requires DNS name comparisons to be case-insensitive, so this implementation diverges from the standard. The flaw is limited to the excluded subtrees constraint path and only applies to certificate chains rooted in a trusted CA — self-signed or otherwise untrusted chains are not affected. The fix is tracked in the Go issue tracker and code review system (Go CL 763763, Go Issue 78332, GitHub Advisory).

Successful exploitation allows an attacker who controls a certificate with a wildcard DNS SAN (using a different case than an excluded DNS constraint) to bypass name constraint enforcement, causing a Go application to accept a certificate it should reject. This enables man-in-the-middle (MITM) attacks against TLS connections in applications using Go's crypto/x509 for certificate validation, potentially exposing sensitive data in transit and compromising the integrity of authenticated communications. The confidentiality impact is rated High (unauthorized access to encrypted traffic), with a Low integrity impact (ability to present forged certificates), and no availability impact (GitHub Advisory, Go Advisory). Downstream products built with affected Go versions — including IBM Instana Observability, IBM App Connect Enterprise, and various open-source tools — are also affected and require recompilation (IBM Advisory).

There is no public proof-of-concept exploit and no evidence of in-the-wild exploitation as of the time of this report (GitHub Advisory). The EPSS score is approximately 0.005% (very low probability of exploitation in the next 30 days). The vulnerability is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog. Exploitation requires an attacker to obtain or forge a certificate with a wildcard DNS SAN that differs in case from an excluded constraint, and then position themselves to perform a MITM attack against a target using a vulnerable Go application — a non-trivial precondition (Go Advisory).

1. Identify a target application: Find a Go application (compiled with Go 1.26.0 or 1.26.1) that performs TLS certificate validation using crypto/x509 and relies on excluded DNS name constraints in its trusted CA certificates.
2. Obtain a certificate with a case-variant wildcard SAN: Acquire or forge a certificate from a trusted CA (or a CA trusted by the target) with a wildcard DNS SAN (e.g., *.EXCLUDED-DOMAIN.COM) that differs in case from the excluded DNS constraint (e.g., excluded: excluded-domain.com).
3. Position for MITM: Use network-level techniques (ARP spoofing, DNS poisoning, BGP hijacking, or rogue Wi-Fi) to intercept TLS traffic between the target client and a server in the excluded domain.
4. Present the forged certificate: Serve the case-variant wildcard certificate during the TLS handshake. The vulnerable Go crypto/x509 library will fail to match the excluded constraint due to case sensitivity and accept the certificate as valid.
5. Intercept traffic: Decrypt and inspect or modify the TLS session, achieving confidentiality and integrity compromise of the communication (GitHub Advisory, Go Advisory).

• Network: Unexpected TLS certificates presented to Go-based services with wildcard SANs using mixed or uppercase domain names that should be excluded by name constraints; TLS handshakes completing successfully for domains that should be blocked by certificate policy.
• Logs: Application TLS connection logs showing successful certificate validation for domains matching excluded DNS constraint patterns (with case differences); certificate details in logs showing SANs like *.DOMAIN.COM where domain.com is in the excluded subtrees.
• File System: Go binaries with build metadata indicating Go version 1.26.0 or 1.26.1 (detectable via go version -m <binary> or govulncheck); presence of unpatched Go toolchain installations.
• Process: Use of govulncheck against deployed Go binaries to identify those linked against the vulnerable crypto/x509 package (oss-security).

The primary remediation is to upgrade Go to version 1.26.2 or later, which contains the fix for this vulnerability (Go Advisory, Go CL 763763). For Azure Linux 3 systems, Microsoft has released patched packages azl3_golang_1.26.1-1 and azl3_golang_1.25.8-1 (Microsoft MSRC). Critically, all Go applications compiled with the affected versions (1.26.0–1.26.1) must be recompiled with the patched Go toolchain, as the vulnerability is in the statically linked standard library — updating the Go runtime alone is insufficient for already-compiled binaries. Use govulncheck to identify which deployed binaries are affected, and prioritize rebuilding applications that perform TLS certificate validation with name constraints (oss-security). IBM has issued advisories for affected products including Instana Observability and App Connect Enterprise (IBM Advisory).

The Go security team announced the fix as part of the Go 1.26.2 and Go 1.25.9 releases, which addressed 10 security fixes in total (golang-announce). Discussion on the oss-security mailing list highlighted a broader concern about the propagation of Go standard library CVEs into compiled binaries distributed by Linux distributions and open-source projects, with community members noting that many distributions (Debian, Ubuntu, Alma) had not yet recompiled affected Go applications (oss-security). Dimitri Ledkov noted that Wolfi and Chainguard had already triggered over 400 rebuilds for this CVE and advocated for symbol-level CVE tracking in govulncheck to reduce unnecessary mass rebuilds (oss-security). Multiple downstream projects including rclone, Portainer, CloudNativePG, and CoreDNS issued updated releases incorporating the patched Go toolchain.