Apple, Google, Microsoft and Mozilla have blocked eight certificates issued by eMudhra, a certificate authority based in Bangalore. The reason: the private keys behind them were so trivial that they could be calculated from the public certificates. If you use an up-to-date Safari, Chrome or Firefox, there is nothing for you to do. The remaining risk lies with software and devices that do not rely on the browsers’ blocks.
What happened
On 17 October a researcher known as Wayne reported the problem to the people who run the browsers’ trust programmes. As proof, he signed a message with each of the eight keys. Researcher Scott Helme then reconstructed them in under a second: one of them was simply the number 4, when a key of this kind should be a random 384-bit number.
The certificates involved are eight intermediate authorities: six are used to secure websites, two for code signing. With an authority’s private key, an attacker could issue fake certificates for any site and have them accepted by browsers and apps. They would, however, need to intercept the traffic between the two parties, which is not a trivial attack.
According to eMudhra, the origin is a key-generation ceremony held on 30 April 2025: an encryption and decryption step is said to have produced a second set of weak keys alongside the strong ones, and the former were mistakenly the ones that ended up in the certificates. The company rules out any breach of its own infrastructure and says it is still investigating the exact cause.
Who has already reacted
- Chrome and Firefox: blocked within a few hours of the report, with no need to update or restart. Google will also remove the root certificate involved, emSign ECC Root CA – G3, from the Chrome Root Store from 27 October.
- Apple: block active since 19 October in Safari, Mail and in apps that use the system’s networking and security frameworks.
- Android: block rolled out through Google Play Services, also from 19 October.
- Microsoft: block from 20 October.
Google stressed that no website certificate derived from these authorities appeared in the public Certificate Transparency logs before the block. There is currently no evidence of abuse.
Where the problem remains
The sticking point lies outside the browsers. Many programs do not check revocations or Certificate Transparency and continue to trust a certificate until their own list of certificates is updated. This is the case with command-line tools, containers, API clients and devices with their own trust store.
There is an exception on the Mac too: some terminal tools may still accept the compromised certificates. Apple is preparing a macOS update that will modify the file /etc/ssl/cert.pem, without giving a date. In the meantime, anyone using those tools can manually remove the affected root certificates from that file.
On the Linux and development side, updates have already been released for Go, Python (certifi), pip, uv, Electron and for the ca-certificates packages of Ubuntu, Debian, Fedora, Arch and Alpine. Other reports, meanwhile, indicate that Signal, WhatsApp and WireGuard are unaffected, because they do not rely on TLS for confidentiality.
What an ordinary user should do
Very little: keep the operating system and browser up to date, and install the macOS updates when they arrive. Anyone running a site with certificates tied to the emSign root must switch to another authority before 27 October. And anyone who sees certificate errors in company apps should never disable verification: that would remove the very protection that has just been restored.
What we think
The big players reacted quickly: Chrome and Firefox within hours, Apple and Microsoft within three days. The case shows, however, how much the certificate authority system depends on a single error in a key-generation ceremony that nobody rechecked for over a year. The fact that the key was the number 4 suggests that a basic automated check could have stopped it.
The long tail outside the browsers is the part to watch. For the average user the likely damage is minimal, but routers, smart-home devices and forgotten servers rarely receive these updates. For Italy there is little to fear on the front of national digital signatures: eMudhra states that its digital-signature business in India runs on separate infrastructure, and the affair concerns only its global arm for website certificates, about 1% of revenue. For those who work in security, it remains a concrete reminder: every trust store built into an app needs updating like any other dependency. As we saw in our article on Google Messages’ advanced protection, the most effective defences remain those that update themselves.
Written by the SpazioiTech newsroom with the help of AI tools, from facts verified across at least two independent outlets, and checked before publication. Spotted a mistake? Tell us.
Translated from the Italian original. Read in Italian
