CVE-2026-33810: Go crypto/x509 wildcard DNS name-constraint validation bypass
- Vendor
- Golang
CVE-2026-33810 is a certificate-validation vulnerability in Go's crypto/x509 package. During certificate-chain verification, excluded DNS name constraints are incorrectly applied to wildcard DNS subject alternative names when the wildcard name uses different letter casing than the constraint. Consequently, a certificate chain that should be rejected for violating an excluded DNS constraint may be accepted. The vulnerability affects only otherwise trusted chains anchored in a root CA contained in VerifyOptions.Roots or the system certificate pool; it does not independently make an untrusted chain trusted.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Applications may accept certificates covering DNS names that their certificate-chain constraints were intended to exclude, undermining certificate-based authentication. Depending on application behavior and the attacker's ability to present the certificate in a connection, this could facilitate endpoint impersonation or interception, exposing sensitive information and enabling limited modification of communications. The assigned CVSS v3.0 vector indicates high confidentiality impact, low integrity impact, and no availability impact.
Mitigation
If you can’t patch tonight, do this now.
No verified vulnerability-specific workaround is documented. As an interim risk-reduction measure, review and restrict trusted roots and accepted certificate chains where operationally feasible, and avoid relying solely on excluded DNS constraints to enforce certificate trust boundaries. These measures do not replace the validation fix.
Remediation
Patch, then assume compromise.
Apply vendor updates addressing CVE-2026-33810 to Go and affected applications that incorporate its certificate-verification implementation. Rebuild and redeploy internally maintained Go applications using a corrected toolchain. For packaged applications, install the applicable distribution updates, including those for Grafana, grafana-pcp, Git LFS, Delve, and rhc-worker-playbook where affected. Exact upstream affected-version ranges and the first fixed Go release are not available in the vulnerability-specific details; use the applicable vendor advisory to identify corrected builds.
Exploits
No public exploits tracked yet. Mallory keeps watching.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
References
Frequently asked questions
- Is CVE-2026-33810 exploited in the wild?
- As of Nov 14, 2026, Mallory has no reports of CVE-2026-33810 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2026-33810?
- As of Nov 14, 2026, Mallory has found no public exploit for CVE-2026-33810.
- Is there a patch for CVE-2026-33810?
- Apply vendor updates addressing CVE-2026-33810 to Go and affected applications that incorporate its certificate-verification implementation. Rebuild and redeploy internally maintained Go applications using a corrected toolchain.
- What products are affected by CVE-2026-33810?
- Golang Go.
- How severe is CVE-2026-33810?
- CVE-2026-33810 has a CVSS v3.1 score of 8.2 (High) and an EPSS score of 0.35% (29th percentile) as of Nov 14, 2026.
Recent activity
131 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.