Skip to main content
Mallory
HighVulnerability

CVE-2026-33810: Go crypto/x509 wildcard DNS name-constraint validation bypass

Published Apr 8, 2026 · Updated 3 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days20 mentions · peak 9 in a dayToday
CVSS8.2High · v3.1
EPSS0.35%29th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Golang
IdentifiersCVE-2026-33810CWE-1289 · Improper Validation of Unsafe…

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.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

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.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

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.

VendorProductType
GolangGoapplication
FAQ

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.
Activity feed

Recent activity

131 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
tenable nessus pluginsNews · Nov 14, 2026Rocky Linux 10.2 [CIQ] Security Update: delve / delve-debuginf... | Tenable®A certificate validation bypass in Go's crypto/x509 package caused by incorrect application of DNS constraints. The advisory identifies affected packages on Rocky Linux 10.2 and directs administrators to install security updates. Nessus identifies exposure using self-reported package versions rather than testing the vulnerability.Read more ↗tenable nessus pluginsNews · Nov 14, 2026Rocky Linux 10 [CIQ] Security Update: grafana / grafana-debugi... | Tenable®A certificate validation bypass in Go's crypto/x509 caused by incorrect application of DNS constraints. The advisory identifies affected packages on Rocky Linux 10. Nessus identifies exposure using self-reported version information rather than testing the vulnerability. Package updates are available through CIQ advisory crlsa-2026_97215.Read more ↗tenable nessus pluginsNews · Nov 14, 2026Rocky Linux 10 [CIQ] Security Update: git-lfs / git-lfs-debugi... | Tenable®A certificate validation bypass in Go's crypto/x509 package caused by incorrect application of DNS constraints. The advisory identifies affected packages on Rocky Linux 10. Nessus identifies exposure using self-reported package versions rather than testing exploitation.Read more ↗tenable nessus pluginsNews · Nov 14, 2026Rocky Linux 10 [CIQ] Security Update: grafana-pcp / grafana-pc... | Tenable®A certificate validation bypass in Go's crypto/x509 package caused by incorrect application of DNS constraints. The advisory identifies affected packages on Rocky Linux 10 and directs administrators to install security updates. Nessus identifies exposure through self-reported package versions rather than testing the vulnerability.Read more ↗
+75 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity11Community discussion across Reddit, Mastodon, and other social sources.