eMudhra Certificate Compromise: Eight Broken CA Keys and What Businesses Should Check Beyond the Browser

Eight intermediate certificate authorities run by eMudhra, a certificate authority whose certificates were trusted by the major browsers, had private keys that were generated so badly that anyone could recover them from the public certificates. That means someone could, in principle, create HTTPS certificates for any website that many programs would accept. For a business, the question this week is not "is my browser safe" but "what else on my network still trusts these certificates."

Browsers moved within hours. The slower part is everything else: servers, scripts, appliances, apps that carry their own certificate lists, and the command-line tools on admin and developer laptops.

What happened with eMudhra

On Saturday, October 17, 2026, a security researcher reported the problem to the browser root programs. Google says the Chrome Root Program received the report at 18:05 UTC. eMudhra says Mozilla received it at 20:06 UTC the same day.

The facts from the primary sources:

• What was broken: the private keys for eight eMudhra intermediate certificate authorities. Cisco's advisory says six of them issue TLS (website) certificates at the DV, OV and EV levels, and two issue code signing certificates. Apple's support page gives the same six and two split.
• When the keys were made: eMudhra says the eight intermediates were created in a Key Generation Ceremony on April 30, 2025. The flaw went unnoticed for about 18 months.
• How weak they were: Cisco's advisory says the keys can reportedly be brute-forced within seconds. Google describes them as generated with weak entropy, meaning not enough randomness.
• Why so many devices trusted them: Cisco's advisory states that all eight were cross-signed by Sectigo's AAA Certificate Services root in May 2025, which made the compromised keys trusted by most devices and browsers, including those that do not trust the eMudhra roots directly.
• Revocation: eMudhra says it revoked all eight intermediates on October 18, 2026.

What is confirmed, what is claimed, and what is not known

Confirmed by the researchers and the browser makers:

• The keys were recoverable. The researcher proved it by signing a test message with each intermediate's private key, according to the disclosure site.
• Chrome blocked the intermediates through a CRLSet update at 19:45 UTC on October 17, with no browser update or restart needed. Android devices received an equivalent block through Google Play Services on October 19.
• Firefox also blocked them on October 17 and Microsoft platforms on October 20, according to the researcher site's timeline.
• Apple began blocking the TLS intermediates on October 19 and the emSign ECC Root CA - G3 root on October 23.
• Chrome removed emSign ECC Root CA - G3, the root above the broken intermediates, from the Chrome Root Store, with removal expected on Tuesday, October 27, 2026 for most devices.

Claimed, not independently confirmed:

• eMudhra says no certificates were issued from the eight intermediates, that seven were never used in production, and that its infrastructure and root keys were not compromised.
• Google says no TLS certificates chaining to the affected intermediates were logged to Certificate Transparency before the block.
• Cisco's security team says it is aware of a public announcement but not of any malicious use.

Not known:

• The exact root cause. eMudhra first described a flaw in a key wrap and unwrap step, said on October 21 the root cause was not yet confirmed, and later attributed it to a script error. On October 30 it appointed KPMG as an independent external reviewer.
• Whether anyone else recovered the keys during those 18 months. Nobody has published evidence either way.

Why browsers are mostly safe and other software may not be

Chrome, Safari and Firefox check Certificate Transparency, a set of public logs that every trusted website certificate must appear in. A forged certificate that was never logged gets rejected. The researcher site notes that browsers enforcing this were therefore likely not attackable, but software that does not check these logs may be.

That covers a lot of business software: backup agents, payment and API integrations, monitoring tools, Java and Python services, and network appliances. Apple's own page, published October 29, says command-line tools on macOS that read /etc/ssl/cert.pem, such as curl, git, python3, ruby, perl and openssl, are not yet covered by its block. Apple says a future software update will fix that. The researcher site added on October 28 that macOS 27.2 undid some fixes users had applied by hand.

Cisco's advisory lists products with fixes, products fixed in the cloud, and products still under investigation. For example, it lists ISE 3.5P5 for December 2026 and IOS XR 26.4.1 for November 30, 2026.

Does this affect my website's SSL certificate?

Only if your certificate came from eMudhra. If it chains to emSign ECC Root CA - G3, Chrome stopped trusting it after the October 27 removal. Google's advice to site operators was to replace it with a certificate from another hierarchy in the Chrome Root Store.

eMudhra said on October 28 that it is winding down its publicly trusted TLS business. Since October 22 it has offered affected TLS customers Sectigo certificates at no cost.

What to do this week

Why this matters for a company network

Most businesses know which website certificates they buy. Very few know every list of trusted certificates their software carries. Each operating system has one. So does Java, Python, many backup and monitoring agents, firewalls, phone systems and SaaS connectors. When a certificate authority fails, the browsers fix themselves in hours, and everything else waits for someone to notice.

In this case the cross-signing means the trust reached far beyond eMudhra's own customers. A business that never bought anything from eMudhra could still have servers that trusted these intermediates until updated.

eMudhra certificate compromise questions people are asking

Is my web browser safe from the eMudhra certificates?

Current versions of Chrome, Firefox, Edge and Safari are protected by automatic blocks. Keep them updated.

Was eMudhra hacked?

eMudhra says no: its systems were not breached and the problem was weak keys created during its own key ceremony. That is its claim, and an external review is under way.

Do I need to replace my SSL certificate?

Only if it was issued by eMudhra or chains to an emSign root. Check the issuer on your certificate.

Were fake certificates used in attacks?

No public evidence shows that. Google says none were logged before the block, and Cisco says it knows of no malicious use. It is not proven that none were ever created.

What is a certificate authority compromise?

A certificate authority vouches for websites and software. If its signing key is exposed, an attacker can create certificates that look legitimate, which allows impersonation and interception of encrypted traffic.

Does this affect code signing?

Two of the eight intermediates issued code signing certificates. Apple says its frameworks do not trust them. Other platforms rely on the revocation and blocks described above.

The bigger lesson

A single error in an 18-month-old key ceremony became a problem for software around the world because trust is inherited quietly. The businesses that recover fastest are the ones that know where their trust lists live and who updates them. Patch the browser, yes, but also inventory the servers, appliances and tools that make their own trust decisions.

Need help checking trust stores and certificates across your systems? See our security hardening service or request a quote.

Get security alerts like this by email, along with our free checklist, at /security-alerts.

Sources: Cisco Security Advisory: Emergency Distrust of eMudhra Root and Intermediate Certificate Authorities; Google: Protecting Chrome and Android Users from Compromised eMudhra Intermediate CA Certificates; Apple Support: About the compromised eMudhra intermediate CAs; eMudhra Statement on Recent Certificate Security Incident; eMudhra Intermediate CA Compromise disclosure site.