Eight Bits of Trust; eMudhra's CA keys cracked in milliseconds

In October 2026, researchers discovered that eight eMudhra intermediate certificate authorities—six for TLS and two for code signing—used catastrophically weak P-384 private keys. Instead of random 384-bit values, each key was a single-byte number such as 4, 56, or 115, preceded by zeros. Because only 256 possibilities existed, anyone with the public certificates could recover the corresponding private keys almost instantly. The certificates were created in April 2025 and cross-signed by Sectigo. Apple, Google, Microsoft, Mozilla, and eMudhra were notified on October 17. Chrome and Firefox quickly blocked the intermediates, Mozilla removed the eMudhra root, and Chrome announced its removal from a future root store. Certificate Transparency limited the likelihood of undetected browser attacks, and no affected certificates appeared in CT logs. However, many non-browser applications—including curl, Python, Node, Go, Java, package managers, CI/CD systems, cloud tools, and embedded devices—typically trust local CA bundles without checking revocation or CT. Testing showed these clients accepted forged certificates for high-value domains, potentially enabling traffic interception, credential theft, malicious software downloads, and attacks on automated infrastructure. The code-signing keys also created risks because Windows could trust malware signed through the affected authorities. The recommended response is to update operating-system CA stores, language packages, containers, and other software. Unpatchable devices may remain vulnerable until certificate expiry in July 2039. eMudhra later attributed the incident to a ceremony-script bug and human error that caused weak keys to be used.

Build this article’s timeline

Extract dated events, key actors, and open questions using the same timeline analysis available in Signal.

Log in to build

Timeline generation is available to signed-in community members.

Five Ws 🤖 2 AI prefills · 3 still unanswered
Who Who are the key actors in this story?
What
In October 2026, researchers discovered that eight eMudhra intermediate certificate authorities—six for TLS and two for code signing—used catastrophically weak P-384 private keys.
🤖 AI prefill
When When did this happen, or what is the timeframe?
Where Where did this occur?
Why
Centers on eMudhra intermediate certificate private keys, single-byte P-384 private keys, and elliptic-curve cryptography
🤖 AI prefill

Login to answer and earn XP for each gap you fill.

Weak CA Private Keys eMudhra, private keys, P-384, single-byte keys, elliptic curve Certificate Revocation Response Chrome, Firefox, Mozilla, CRLSet, OneCRL Nonbrowser TLS Exposure curl, Python, Node, Java, CA bundles Attack Impact Scenarios man-in-the-middle, TLS interception, code signing, IoT, firmware Remediation And Root Cause CA bundle updates, HSM, CSR, human error, firmware
eMudhra intermediate certificate private keys100% single-byte P-384 private keys99% elliptic-curve cryptography94% public-key recovery by brute force94% certificate authority compromise92% TLS issuing certificate authorities90% code-signing certificate authorities89% Certificate Transparency87% certificate revocation and root-store updates87% non-browser TLS clients86%
57
Manipulation Score: Medium How much this article uses emotional framing vs. straight reporting
Loaded Language 4825%
Absolutist 5215%
Threat/Panic 7225%
Us vs Them 1815%
Engagement Bait 3820%
Manipulation score look right?

Factual Claims (10)

high technology
Eight eMudhra intermediate certificate private keys were weak single-byte values, including 4, 56, and 115, and could be recovered from public certificates.
high technology
The affected certificates used P-384 elliptic-curve keys whose private values had 47 zero bytes followed by one byte.
medium technology
The eight affected intermediates consisted of six TLS issuing CAs and two code-signing CAs created in April 2025.
medium technology
All eight intermediates were cross-signed by Sectigo's AAA Certificate Services root in May 2025.
medium technology
Chrome and Firefox blocked the affected intermediates, Mozilla removed the eMudhra root, and Chrome planned to remove the root from its Chrome Root Store.
high technology
Anyone who had viewed one of the certificates since April 2025 could have recovered its private key in milliseconds using commodity hardware.
medium technology
Many non-browser TLS clients do not check revocation or Certificate Transparency by default and may continue trusting the affected certificates.
high technology
A forged certificate for any hostname could be used to intercept traffic from vulnerable devices if an attacker obtained a network position.
high technology
Windows may trust malware signed through the affected eMudhra code-signing chain when revocation is not checked.
medium technology
eMudhra attributed the incident to a ceremony-script bug, creation of a second weak key pair on an HSM, and human error selecting the wrong keys for the CSR.

Comments

Login to view and post comments.

🏠Portal 📰Links ❓Q&A 📅Events 💼Jobs