Eight intermediate Certificate Authorities operated by eMudhra had their private keys compromised. Six of them issue TLS certificates, meaning anyone holding those keys could mint certificates that browsers and apps would accept as valid for any domain on the internet. eMudhra and Sectigo have revoked the affected certificates, and Apple began blocking them on 19 October 2026. The scope is precisely defined: 12 certificates across the six TLS-issuing intermediate CAs, each having two chains — one through emSign Root TLS CA - G3 (chaining to emSign ECC Root CA - G3) and one cross-signed by Sectigo (chaining to AAA Certificate Services). Apple also began blocking the emSign ECC Root CA - G3 root certificate itself on 23 October 2026. For most Apple users, the fix is invisible. Safari, Mail, and any app using Apple's networking and security frameworks already reject these certificates via automatic certificate configuration updates pushed to devices. No software update required, no user action needed. The gap lives in the command line. Tools like curl, git, python3, ruby, perl, and openssl that ship with macOS or Xcode Command Line Tools validate certificates against /etc/ssl/cert.pem — a static file that doesn't check Apple's block list or revocation status. Until a future macOS update patches this file, these tools will happily accept forged certificates signed with the compromised keys. Apple provides a manual workaround: administrators can remove the emSign ECC Root CA - G3 and optionally AAA Certificate Services root certificates from /etc/ssl/cert.pem using provided awk commands. The tradeoff is real — removing these roots will also break verification of legitimate certificates chaining through unaffected intermediate CAs under the same roots. And any macOS software update can silently replace cert.pem, requiring the process to be repeated. The architectural lesson is familiar. Apple maintains two separate trust evaluation paths — the framework-level trust store (dynamic, updatable, revocation-aware) and the file-based POSIX trust store (static, dumb, updated only with OS releases). This split means a compromise that's handled in minutes for Safari can linger for weeks or months in developer toolchains, CI/CD pipelines, and server-side scripts. The incident underscores the fragility of the CA ecosystem's trust model. A single intermediate CA compromise cascades through multiple trust chains (emSign and Sectigo), affects every relying party globally, and the remediation burden falls on individual system administrators hand-editing certificate bundles. The Web PKI's centralized trust hierarchy remains its greatest efficiency and its greatest vulnerability.
