eMudhra’s Security Key Flaw: What Went Wrong And Why Google, Mozilla Stepped In

Eight intermediate certificate authorities operated by eMudhra had private keys that could be reconstructed from publicly available certificates. The keys were not stolen from company systems. They were created from extremely small, guessable numbers, making them unsafe. This mattered because certificate authorities help establish trust for websites and software.

The affected values were 4, 56, 66, 115, 155, 156, 230, and 237. A researcher named Wayne recovered the keys and demonstrated control by signing a message with each one. Mozilla independently recovered the same keys on the report date, October 17, 2026. The finding was reported to browser security teams.

Google, Mozilla, Apple, and Microsoft responded by blocking or distrusting the affected certificates. That step reduces the chance of fraudulent certificates being accepted. It can also force legitimate users to replace certificates if a trusted parent certificate is withdrawn. eMudhra said no end-user or website certificates had been issued through the eight authorities, but replacement work and investigations continue.

A certificate authority, or CA, issues digital certificates that connect an online identity with a public key. Browsers rely on trusted CAs to help determine whether a website is what it claims to be. This supports HTTPS, the security system used when people connect to websites.

A website presents a certificate to a browser. The certificate identifies the website and is signed by a CA, directly or through intermediate authorities. The browser checks the signatures, dates, names, and whether the issuing authority is trusted. If those checks succeed, the browser can establish an encrypted connection and display the site as trusted, subject to other checks.

The incident shows why CA security matters beyond one company. If a CA private key is exposed or weak, someone may create a certificate for an unauthorised website. Browsers could then mistake that site for the real one. eMudhra said the affected authorities had not issued certificates to end users or websites, and no successful malicious attack was publicly established.

The incident involved eight private keys belonging to eight intermediate certificate authorities. Six keys were used for website security, also called TLS, while two were intended for code signing. Website certificates help browsers trust HTTPS connections. Code-signing certificates help establish trust in software and its publisher.

The eight weak values were 4, 56, 66, 115, 155, 156, 230, and 237. A researcher reconstructed each corresponding private key from public certificates and proved control by signing a message. The keys were created during a ceremony on April 30, 2025, when a process flaw generated weak keys alongside intended strong ones.

The affected business was limited in financial terms, contributing around 1% of eMudhra’s revenue. eMudhra said its Indian digital signature and eSign operations were separate and continued normally. However, the company acknowledged that reputational damage could not yet be quantified. It was working with potentially affected customers on replacement certificates.

Private keys are supposed to be extremely difficult to guess. In this case, a flaw in eMudhra’s key-generation ceremony created a second set of weak keys alongside the intended strong ones. Staff mistakenly used those weak keys when preparing certificates. The company said it was still investigating the precise error.

The weak keys came from extremely small numbers: 4, 56, 66, 115, 155, 156, 230, and 237. Because those values were easy to guess, researcher Wayne could use publicly available certificates to reconstruct the corresponding private keys. He then signed a message with each key, demonstrating control. Mozilla independently recovered the same keys.

This was therefore a generation failure, not evidence that attackers broke into eMudhra’s systems and stole keys. eMudhra said its core infrastructure was not compromised, no data was breached, and security controls remained intact. The discovery still made the certificates unsafe, because anyone who recovered the same keys could potentially create certificates using the affected authorities.

A certificate authority’s private key is used to support trust in certificates. If an attacker obtains that key, they may be able to create a certificate for a website or software publisher without permission. Browsers or applications could then treat the unauthorised item as legitimate, depending on their trust checks.

For a website, a fraudulent certificate could help an attacker impersonate the real site and, in certain circumstances, intercept or modify communications. Two affected eMudhra keys were intended for code signing. That creates a related risk: malicious software could be presented as digitally signed by a trusted source, though the article does not report such an attack.

There is no public evidence that the compromised keys were used successfully in a malicious attack. eMudhra said the eight authorities had not issued certificates to end users or websites, based on public records. Browser makers nevertheless blocked or distrusted the certificates to reduce future risk and protect systems that might otherwise accept them.

Browser companies withdrew trust because the eight private keys were no longer reliable proof of identity. A researcher had reconstructed them from public certificates, and Mozilla independently confirmed the result. Any certificate signed through a compromised authority could therefore be treated as potentially fraudulent, even if no attack had been observed.

The practical response was to block or distrust the affected certificates. Browsers, applications, and enterprise systems that relied on those certificates might reject connections or signed software. The article also highlights a second problem: withdrawing trust in a parent certificate can affect legitimate certificates beneath it. Businesses may need to replace certificates to keep critical services operating.

The disruption may be limited because eMudhra said none of the eight authorities had issued certificates to end users or websites. Still, the company was working with customers who might be affected. Its investigation into the root cause and security controls was ongoing, while the reputational impact remained unquantified.

Public-key cryptography uses a public key that can be shared and a private key that must remain secret. A certificate links a website or software identity to its public key. The matching private key proves control. This matters because eMudhra’s weak private keys could be reconstructed from public certificates, breaking the intended protection.

Certificates usually form a chain. An intermediate certificate authority is authorised by a parent or root authority, while browsers keep trusted roots in trust stores. A browser checks the signatures through that chain before accepting a certificate. Certificate Transparency adds public records of issued certificates, allowing researchers and security teams to look for suspicious issuance. The article’s researcher used public certificates to recover the weak keys.

These safeguards work together, but they cannot compensate for badly generated private keys. Browser makers can remove trust when a key is compromised, as they did here. eMudhra said its root private keys and other intermediate authorities were unaffected. The article does not describe every technical check, so these broader cryptographic details provide necessary context.