You are using an out of date browser. It may not display this or other websites correctly. You should upgrade or use an alternative browser.
x509
About this tag
The x509 tag on WindowsForum.com covers discussions about X.509 certificate validation, including recent CVEs in Go's crypto/x509 library such as CVE-2026-27137 (email name constraints bug), CVE-2025-58188 (DSA denial of service), and CVE-2025-61727 (wildcard SAN exclusion bypass). It also includes Microsoft's upcoming enforcement of strong certificate mappings on Windows domain controllers, which affects Kerberos and Active Directory certificate-based authentication. Topics focus on certificate chain verification, name constraints, security patches, and migration planning for enterprise IT environments.
A subtle correctness bug in Go’s X.509 verification code — tracked as CVE-2026-27137 — can cause certificate chains to ignore multiple email-address name constraints when those constraints share the same local-part but differ by domain. The practical upshot: under specific conditions a...
A high-severity bug in the Go standard library — tracked as CVE-2025-58188 — can cause programs to panic during X.509 certificate validation when a certificate chain contains a DSA public key, enabling an attacker to induce denial-of-service conditions against any application that validates...
An important validation bug has been published against the Go standard library’s certificate-handling code: CVE-2025-61727 describes an improper application of excluded DNS name constraints when verifying wildcard names in crypto/x509, meaning that an excluded-subdomain constraint in a...
Microsoft will remove support for the StrongCertificateBindingEnforcement registry key on Windows domain controllers on September 10, 2025, forcing a permanent switch to stricter, strong certificate-to-account mappings that will break legacy certificate-based authentication setups unless...