Yesterday's urgent Go release distrusted eight unnamed intermediates. They're now public: eMudhra's EM DV / OV / EV TLS CA - G3B and G3C (six TLS CAs) plus two code-signing CAs, all from one April 30, 2025 key ceremony. Mozilla's Dennis Jackson found that the eight P-384 private keys were integers below 256, so anyone could recover them from the public certificates almost instantly. A researcher reported this on Oct 17 with signed proof for all eight keys. Chrome blocked the keys via CRLSet that evening and Firefox via OneCRL; Apple followed on Oct 19 and Microsoft on Oct 20. eMudhra revoked the intermediates on Oct 18 (reason cACompromise) and Sectigo revoked its cross-signs on Oct 19. No TLS certificate from these CAs appears in Certificate Transparency logs, so clients that enforce CT (Chrome, Firefox, Safari, Edge) couldn't have been attacked. For clients that don't check CT, nobody knows whether the keys were abused. eMudhra says one of the intermediates was in production and none issued end-entity certificates. Chrome removes emSign ECC Root CA - G3 from its root store around Oct 27 (PDT), and NSS 3.131.1 removes it as well. On the Go issue, Roland Shoemaker explained that the release notes were deliberately vague so attackers wouldn't get a head start. Filippo Valsorda added that Linux trust stores have no way to propagate revocation, so the only option was hard-coding the keys.
ca-certificates, certifi 2026.10.19, rustls-webpki 0.103.16 and cloudflared 2026.10.2; Node.js and Bun are still pending. Action: rebuild Go services on the fixed release and update the ca-certificates package in your base images (Go 1.25 and older depend on the system pool). Check the CA bundles you use to verify mTLS client certificates. Test the path each application actually uses (the incident site has test hosts; a passing curl doesn't prove your service is safe). If new certificate errors appear, don't fix them by turning off verification. Links: tracker + patched packages Β· Google Β· Cloudflare Β· go.dev/issue/82345.