Futureweb

Privacy

Browsers blocked eight eMudhra intermediate certificates after a report of weak keys. The company says its infrastructure was not breached.

Google says eight eMudhra intermediates had weak keys and were blocked October 17. The company says a 2025 ceremony published them and that its infrastructure was not breached.

The short version

Google's security post says a researcher reported on October 17, 2026 that eight eMudhra intermediate certificates had weak private keys, and that Chrome blocked those keys the same day. eMudhra says a 2025 key ceremony published the weak keys, that it revoked the eight intermediates, and that its infrastructure and its India signature business were not compromised. Mozilla published its own protective steps.

A report on October 17, a statement on October 21

Google's Chrome root-program post says that on October 17, 2026, at 18:05 UTC, a researcher reported weak private keys for eight eMudhra subordinate certificate authorities. By 19:45 UTC Chrome had blocked those keys for Chrome users, and an Android update followed through Play services. Mozilla's October 20 post says it received the report the same evening and took steps to protect Firefox users. eMudhra's statement, dated Bengaluru, October 21, is the company's account. Ars Technica's story is what the privacy wire carried. The sources here are the company and the two browser programs.what a session cannot be.

Weak keys, as the company describes the ceremony

eMudhra says the eight intermediates were created under its ECC root in a ceremony on April 30, 2025, using hardware security modules. A flaw in that ceremony caused a wrap step to produce a second set of weak keys beside the original strong keys, and the weak keys were the ones published into browser trust lists. The company says the certificates had passed audits and had been trusted since mid-2025. It says a researcher found the weakness and reported it to Apple, Google, Microsoft, and Mozilla. This page does not describe how a weak key is recognized. The fact is the report and the company's account of which keys were published.OPM's access grant was unlawful.

What the company says did not happen

The statement says infrastructure was not compromised, no data was breached, and physical and logical controls stayed intact. It says the India digital-signature and eSign businesses are separate and unaffected. It also says no certificates had been issued from the eight intermediates, and that they were revoked the day after the report. A revocation is the company's action. A browser block is the root programs' action. They are both in the record, and they are not the same document.the key stays with the holder.

What the browsers say the keys could allow

Google says keys generated with too little randomness would let someone forge a trusted certificate for any website, for a client that still trusted those authorities. Mozilla's post says the same kind of impersonation was the risk it was closing. Both posts are about clients that had not yet removed trust. Google adds that it did not see website certificates chained to six of the intermediates in public certificate logs before the block, which limits what could have been used against browsers that require those logs. The six and the eight are both in Google's post. This page leaves the difference standing rather than guessing which count a reader should prefer.Chrome's warning is a product setting.

Who had to ship a software update

Google says Chrome users were covered by a block on the keys themselves, without a browser update or a restart, and that Android received an equivalent update through Play services, with a restart as a way to pull it sooner. Mozilla's post is the Firefox side of the same hour. A person who does not use those trust stores is outside those two writeups. Applications that carry their own copy of the trust list are the remaining case, and these three sources are not a full inventory of those applications.the privacy desk.

No key material on this page

The posts identify the incident by the company's name, the count, and the dates. They also contain technical fingerprints for engineers. This page does not reprint those fingerprints. The public fact a reader needs is which trust programs acted, what the company says failed in the ceremony, and what the company says was not breached. Asked directly, How many certificates? Google's post says eight subordinate certificate-authority certificates. eMudhra's statement says eight of its global TLS intermediates. Both documents use eight. This page does not print the key material.Muse share pages were findable.

Who is in scope

People whose software still trusted the affected global TLS intermediates on October 17, until the block or update arrived. eMudhra's India signature customers are out of scope on the company's statement. Website owners who never received a certificate from these intermediates are in scope only as names that could have been impersonated to a client that still trusted the keys, which is the risk Google states, not a list of affected sites.what RPKI checks on a route.

What stays on the record

October 17, 2026 report. Eight eMudhra intermediates. Chrome blocked the keys the same day. Mozilla published protections October 20. eMudhra on October 21: weak keys from an April 30, 2025 ceremony, intermediates revoked, no certificates issued from them, infrastructure not compromised, India signature business unaffected. Google's later sentence about six intermediates left as Google wrote it. Asked directly, When was the report? Google says Saturday, October 17, 2026, at 18:05 UTC, and that Chrome had corroborated the finding and blocked the keys by 19:45 UTC, without requiring a browser restart. Mozilla says it received a report the same evening.Futureweb.

What would move the row

A finished root-cause report from the company, or a browser version note that removes a root rather than only the intermediates, would be a later document. On October 22 eMudhra said its board will leave the global SSL and TLS business. That exit does not replace the report still owed. The record of this row is the report, the blocks, and the company's denial that its infrastructure was breached. Google's security post says a researcher reported on October 17, 2026 that eight eMudhra intermediate certificates had weak private keys, and that Chrome blocked those keys the same day. eMudhra says a 2025 key ceremony published the weak keys, that it revoked the eight intermediates, and that its infrastructure and its India signature business were not compromised. Mozilla published its own protective steps.eMudhra leaves the TLS business.

Sources

The reports this brief is filing. Futureweb did not republish them.

  1. eMudhra statement
  2. Google Chrome root program
  3. Mozilla Security

Questions

How many certificates?

Google's post says eight subordinate certificate-authority certificates. eMudhra's statement says eight of its global TLS intermediates. Both documents use eight. This page does not print the key material.

When was the report?

Google says Saturday, October 17, 2026, at 18:05 UTC, and that Chrome had corroborated the finding and blocked the keys by 19:45 UTC, without requiring a browser restart. Mozilla says it received a report the same evening.

What does eMudhra say went wrong?

Its October 21 statement says a key-generation ceremony on April 30, 2025 produced a second, weak set of keys in a wrap step, and that the weak keys were the ones published. It says it is still establishing the root cause. It does not describe a break-in.

What does the company say was not hit?

Infrastructure was not compromised, no data was breached, and the India digital-signature and eSign businesses run on separate infrastructure and are unaffected. The statement says no certificates had been issued from the eight intermediates.

Why do Google's six and eight both appear?

The post's opening count is eight certificates. A later sentence says no publicly logged website certificates chained to six of the intermediates before the block. This page does not collapse those two counts into one.