Skip to main content
Mallory
← Back to News
identity-authentication-vulnerabilityopen-source-dependency-vulnerabilitywidely-deployed-product-advisory

Go crypto/x509 Flaw Lets Wildcard Certificates Bypass Excluded DNS Constraints

Vulnerability Disclosure · 5 sources · Updated 5mo ago · First seen Apr 28, 2026

Go crypto/x509 Flaw Lets Wildcard Certificates Bypass Excluded DNS Constraints

Go disclosed CVE-2026-33810, a certificate validation flaw in crypto/x509 in Go 1.26 that can cause excluded DNS name constraints to be enforced incorrectly for wildcard Subject Alternative Names. The bug appears when a wildcard SAN such as *.example.com is evaluated against an excluded constraint written with different letter casing, such as EXAMPLE.COM, allowing the wildcard domain to bypass the exclusion during certificate chain verification.

The issue affects otherwise trusted certificate chains anchored in VerifyOptions.Roots or the system certificate pool, narrowing exposure to chains that already terminate at a trusted root CA. Go tracked the bug as issue #78332, credited the report to Riyas from Saintgits College of Engineering, k1rnt, and @1seal, and later published a fix on the release-branch.go1.26; downstream vendors including SUSE also opened advisories for the vulnerability.

Do you run this?See affected versions and whether adversaries are exploiting it.
Check your exposure
Event timeline

How this story unfolded

Events from the most recent confirmed update back to the earliest known activity.

3 events · Mar 27, 2026 – Apr 28, 2026
  1. Apr 28, 20267mo ago

    SUSE opened bug 1261662 for CVE-2026-33810

    SUSE tracked CVE-2026-33810 in bug 1261662, identifying it as a Go 1.26 crypto/x509 vulnerability involving excluded DNS constraints on wildcard domains. The entry reflects downstream vendor tracking of the disclosed flaw.

    1261662 - (CVE-2026-33810) VUL-0: CVE-2026-33810: go1.26: crypto/x509: excluded DNS constraints not properly applied to wildcard domains
  2. Apr 7, 20268mo ago

    Go committed a fix for wildcard DNS constraint case handling

    A commit on the Go 1.26 release branch addressed the crypto/x509 wildcard constraint map case-handling issue tied to CVE-2026-33810. This represents the code fix for the certificate validation flaw.

    [release-branch.go1.26] crypto/x509: fix wildcard constraint map case… · golang/go@ceb4da6 · GitHub
  3. Mar 27, 20268mo ago

    CVE-2026-33810 was disclosed in Go issue 78332

    Go disclosed CVE-2026-33810 as a certificate validation flaw in Go 1.26's crypto/x509 package. The bug allows excluded DNS constraints to be applied incorrectly to wildcard DNS SANs when letter casing differs, potentially bypassing constraints for otherwise trusted chains.

    crypto/x509: excluded DNS constraints not properly applied to wildcard domains · Issue #78332 · golang/go
Linked entities

Related entities

Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.

Open in app →
Do you run this?See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
Check Your Exposure
Mallory platform

See the full picture, correlated to your attack surface.

This page covers what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which threat actors are using it right now, and what to deploy next.

Exposure mappingMap indicators from this story to your assets and identify affected systems in minutes.
Threat actor evidenceEvery observed campaign, victim, and pivot linked to actors named in this story.
Associated malwareMalware, exploits, and IOCs connected to the activity described here.
Detection signaturesYARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Scheduled alertsGet matching new stories delivered to your team as they break, not the next morning.
AI threadsAsk questions about this story and take action on the answers.