Certificate Authority Blames Faulty Script for Dangerously Weak Digital Certificates
Former certification authority eMudhra has told the Bugzilla community that a faulty Python script is the main reason it issued highly insecure digital certificates. A user named "Naveen Kumar ML" said sixteen issuing CA key pairs were created during a single key-generation ceremony on 30 April 2025. The keys were generated correctly on a hardware security module, then processed by a custom script. That script contained a bug that truncated the private values, so the matching public keys could be worked out from public information. Per The Register, the company appears to have ignored 47 of the 48 bytes in each key, leaving single-byte keys such as the number four.
The company says the script ran only on an isolated host and was not part of its emCA software. It needed the workaround because "global supply chain constraints" stopped it buying the hardware security modules it wanted for certificates intended for use in the USA. It generated keys on Utimaco devices and planned to move them to Crypto4A devices, a step described as unusual. Policy changes on certificate provenance meant new certificates were needed by the end of May. The company did not notice the script errors and did not test the keys it created.
A Mozilla team member then spotted the weak keys and warned that attackers could issue fraudulent certificates to impersonate servers, observe traffic, or modify data in transit. Browser makers quickly updated their software so it no longer recognises eMudhra certificates.