eMudhra revokes eight intermediates for compromise; Go distrusts them

eMudhra revokes eight intermediates for compromise; Go distrusts them

19 October 2026: Eight issuing certificate authorities run by the Indian CA eMudhra under its emSign G3 roots were revoked on 18 October with the reason "cACompromise", and Go 1.27.3 and 1.26.10, released on 19 October as CVE-2026-111943, stop any certificate chain that passes through them. Sites and code-signing customers holding certificates from those CAs need new ones from a different issuer.

Not yet independently verified. Neither eMudhra nor the Go team has said what the security concern is, and we found no statement from eMudhra; the link between the Go fix and eMudhra rests on the CCADB records and the certificates listed on the Go issue. We will update this when it can be confirmed, and remove this note.

Which certificates are affected

The Common CA Database lists the eight as revoked by eMudhra Technologies on 18 October, all valid from 30 April 2025:

Issuing CA	Root	Subject organisation
EM DV TLS CA - G3B, EM EV TLS CA - G3B, EM OV TLS CA - G3B	emSign Root TLS CA - G3	eMudhra BV (Netherlands)
EM DV TLS CA - G3C, EM EV TLS CA - G3C, EM OV TLS CA - G3C	emSign Root TLS CA - G3	eMudhra Inc (United States)
EM OV CS CA - G3B, EM OV CS CA - G3C	emSign Root CS CA - G3	eMudhra BV and eMudhra Inc

The same eight subjects also had cross-signed copies under Sectigo's AAA Certificate Services root, and Sectigo revoked all eight of those on 19 October, also for CA compromise. The six TLS CAs cover domain, organisation and extended validation certificates; the two CS CAs issue code-signing certificates. Older G2A and G3A issuing CAs were retired for cessation of operation in May 2025 and are not part of this.

What the Go release changes

The Go team's issue says it is "blocking trust in a small set of intermediate certificates due to specific security concerns around their operation", that Verify now filters out chains containing them, and that it "highly" recommends upgrading at once. It was handled on Go's urgent security track. The fix shipped as go1.27.3 and go1.26.10, which the release history describes only as security fixes to crypto/x509. Go 1.25 and older get no fix, because only the two newest major versions are supported.

Revocation alone does not stop every client, since many never check revocation lists for intermediates. That is why Go, which ships its own verifier, hard-codes the distrust, and why browsers and operating system root programmes are likely to follow with their own blocklists.

Finding emSign certificates in your estate

• Search certificate inventories and Certificate Transparency logs for the eight issuer names above, including code-signing certificates used on software releases.
• Rebuild Go services on 1.27.3 or 1.26.10; until then a Go client will still accept these chains.
• Expect a TLS failure, not a warning, from any Go-based tool that meets a server still presenting one of these chains.

Company profile on TrustList: eMudhra

Sources

• Go issue 82345: crypto/x509 mitigation for security concerns with a specific Certificate Authority (CVE-2026-111943), 19 October 2026
• Go: release history, go1.27.3 and go1.26.10, 19 October 2026
• CCADB: public intermediate certificates revoked (read 2026-10-20), 20 October 2026