How to Fix CVE-2026-33810: crypto/x509 (Bundle Sibling)

*By Sai Kiran Pandrala*

Last verified: 2026-05-25

CVE-2026-33810 is a sibling vulnerability in the same Go Standard Library crypto/x509 advisory bundle as CVE-2026-32280. The same patched build closes every CVE in the bundle, so the remediation procedure for CVE-2026-33810 matches the primary write-up.

What is different about CVE-2026-33810?

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.

Impact is consistent with the bundle: compromise of the affected component as described in the vendor advisory. The patched build closes every code path in the advisory in one update.

How to fix CVE-2026-33810

Apply the patched build per the primary write-up: How to Fix CVE-2026-32280.

For a quick check, confirm the running version of crypto/x509:

# Confirm the installed version via your package manager
dpkg -l | grep -i crypto/x509   # Debian/Ubuntu
rpm -qa | grep -i crypto/x509   # RHEL/CentOS/Rocky

Frequently asked questions

Is CVE-2026-33810 being actively exploited?

Not at the time of writing. It is not listed in CISA's Known Exploited Vulnerabilities catalog. That status can change, so monitor the vendor advisory and the KEV catalog if the system is exposed.

How severe is CVE-2026-33810?

CVSS rates it 7.5 (High). Use that score to set your patch priority alongside the other items in your queue.

Do I have to take crypto/x509 offline to apply the patch?

It depends on the deployment. High-availability or clustered installs can usually patch one node at a time with no full outage. Standalone installs typically need a short restart. Always follow the vendor's documented upgrade steps.

What if my vulnerability scanner still flags CVE-2026-33810 after I patch?

Re-run the scan after a service restart, then confirm the scanner's plugin set is up to date. Some scanners detect by banner version only and lag the official fix metadata by a release.

References

• Official vendor advisory: https://go.dev/cl/763763
• NVD entry: https://nvd.nist.gov/vuln/detail/CVE-2026-33810
• CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
• Primary write-up: How to Fix CVE-2026-32280

*Written by Sai Kiran Pandrala. Last verified 2026-05-25. Part of the Go Standard Library crypto/x509 advisory bundle. Full procedure at how-to-fix-cve-2026-32280.*