Monday 16 November
Global

Your region, kept on this device.

eMudhra blames buggy script for weak certificates before quitting TLS certification

Severity
High
Sources
1

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 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

  1. Check whether any certificates in use were issued by eMudhra, since browsers have stopped recognising them.
  2. 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

  1. Thu 12 NovemberDisgraced former CA eMudhra blames buggy script for hopelessly weak certificatesThe Register (Security)

Who reported · 1 outlet

The Register (Security)

Who and what is in it

Report a problem