Fedora distrusts eMudhra CAs after trivial private keys leak
Updated ca-certificates package blocks a dozen certificates whose private keys were the integers 4, 56, and 115.
Fedora has shipped an updated ca-certificates package that distrusts a set of eMudhra certificates after researchers disclosed that several of the authority’s private keys were trivially weak integers, including the numbers 4, 56, and 115.
The flaw left intermediate certificates effectively compromised. Anyone who knew or guessed those values could forge signatures under the affected roots. According to discussion on the Fedora project forums, a dozen certificates are in scope, not only the two roots some users first blacklisted by hand. The weak keys had been exposed for roughly 17 months, with no public clarity on whether they were abused in the wild.
Barry A. Scott pointed users at the packaged fix already built for Fedora. Where the stable update is not yet visible, the advisory FEDORA-2026-56e14eb520 can be pulled from updates-testing. Until then, some administrators extracted the offending trust anchors and dropped them into the system blocklist so update-ca-trust would stop honouring them.
Reporting on the disclosure attributed the keys to a buggy script and human error, signing with the wrong file rather than a cryptographically sound key. Commenters on the Fedora thread called the lapse grounds to strip the operator of CA status. A companion test site lets browsers and curl clients check whether a given system still trusts the bad material.
The incident is a blunt reminder that public-key infrastructure fails open when key generation or operational handling collapses to values an attacker can try by hand.