eMudhra blames buggy script for weak certificates before quitting TLS certification
VULNERABILITYeMudhraredteam/daily · 1 source
- Severity
- High
- Sources
- 1
What happened
eMudhra says a defect in a custom Python key-handling script truncated private key values during a key-generation ceremony on 30 April 2025, affecting sixteen subordinate CA key pairs in its B and C series. The keys could be recovered from public information, so attackers could have issued fraudulent certificates to impersonate servers. After a Mozilla team member flagged the weak keys, browser makers stopped recognising eMudhra certificates, and the company said it would wind up its certification business.
For IT people · Written by AI from 1 source · Wrong?
What to do
- Check whether any certificates in use were issued by eMudhra, since browsers have stopped recognising them.
- Replace any affected eMudhra-issued certificates with ones from a trusted certificate authority.
Written by AI from the sources, checked against them
Full story timeline · 1 update
Who reported · 1 outlet
The Register (Security)