Apple has blocked on iOS and iPadOS a set of eight compromised security certificates that were found to be astoundingly weak. It's a bit more complicated on Mac.
Security certificates (SSL/TLS) are used to keep Internet users secure, thanks to using encryption to secure traffic and to verify domain ownership. However, a collection of certificates from one authority has been pulled from use after security researchers found them to be extremely weak.
As a result, Indian certificate authority eMudhra revoked the certificates. This prevents the certificates from being used by websites, closing the barn door after their discovery and disclosure on October 17.
According to Beeping Computer, Google Chrome blocked a set of six compromised intermediates authorized to issue TLS certificates. Meanwhile Mozilla blocked compromised certificates in Firefox.
While Google and Mozilla instigated the blocks on October 17, Apple was a little later in doing so. It added protections in iOS and iPadOS on October 19.
It's not so simple on Mac. More on that in a bit.
Amazingly insecure
The point of a security certificate is that it can let systems identify each other and set up encryption between the two points. That encryption requires the creation of keys, both to set up and to decrypt the data.
This key is usually lengthy and complex, to a level that it would take way too much effort to guess the key or determine it by brute-forcing every possible combination, in a reasonable timeframe. Think along the lines of keys over 100 characters long.
In this instance, the keys for the eight certificates were entirely guessable, even by humans. The compromised private keys were 4, 56, 66, 115, 155, 156, 230, 237.
For clarity, those numbers aren't the lengths of keys. Those are the actual keys for each of the eight certificates.
This is on a par with using a system password of "password" or "123" and hoping it doesn't get guessed.
According to Mozilla's bug reporting system, Mozilla was able to recover the private keys very easily. And the keys were recovered without any prior knowledge of how the original reporter did it.
Impact of an idiotic mistake
Of those eight certificates, six were used for TLS, and were trusted by Apple, Chrome, Microsoft, and Mozilla root programs. The other two are used for code signing and trusted by Microsoft.
Further complicating matters is that these certificates were generated in April 2025, so they have been available for well over a year. However, most of the certificates didn't make it into production, and there's no evidence of attackers recovering or using the keys either.
When it comes to what end users need to do, the advice is fairly simple: update your software as soon as you can. In some cases, like Mozilla's inclusion of the OneCRL system in Firefox, the protections were implemented without requiring a browser update or even a restart.
For Apple users, that means updating their apps, as well as iOS and macOS.
Mac users do still have to be wary, as the built-in curl utility doesn't check revocation information. If the Mac has encountered and trusted the certificates in the past, it will blindly continue to do so going forward.
That said, the assurance that most weren't use and the insistence that attackers haven't taken advantage of it may mean that few Mac users, if any, will be affected.
For eMudhra, in a statement on the matter, it insists there was no infrastructure compromise nor signs of any data breaches. It is also working with customers who may have been affected to replace the certificates.
