Skip to content

DEV Community

← All Trends

eMudhra CA Weak Private Key Incident

19 posts in this trend in the last 7 days • Active about 3 hours ago

Etairos.ai

Oct 22

Eight eMudhra Intermediate CA Keys Were Computable From Public Certificates: Browsers Blocked Them in Hours, Everything Else Needs Patches

#cybersecurity #infosec #security

5 min read

Alan West

Oct 21

eMudhra Certificate Distrust: One CA Key Was 4. How to Check If Your Site Breaks

#security #webdev #devops #linux

8 min read

Taha Echakiri for NeticsLabs

Oct 23

Eight eMudhra Intermediate CA Keys Rested on Eight Bits

#security #opensource #ai #devops

7 min read

Mohammad Taha Azizi Ahad

Oct 27

Eight CA keys were guessable. The padlock never noticed.

#showdev #cryptography #security #webdev

7 min read

jamilxt

Oct 21

After the eMudhra CA Incident, Update More Than Your Browser

#security #tls #devops #tutorial

8 min read

A key so small it could be counted by hand

Varshith V Hegde

Oct 27

The Most Embarrassing Private Key in Web PKI History

#security #webdev #devops #ai

8

10 min read

Dionisio Cortés Fernández

Oct 25

Eight CA Keys Between 1 and 255: What the eMudhra Incident Means for Your Code

#security #java #go #devops

24 min read

Affix Center Softech Services Pvt. Ltd

Oct 22

emSign G3 Revoked: Updating Trust Stores Outside the Browser

#security #tls #devops #sysadmin

2 min read

frank chu

Oct 22

eMudhra quit the CA business today. I checked your trust store — its roots are still in it.

#cybersecurity #infosec #security

4 min read

Oct 22

Eight CA private keys under 256: checking every EC key in CCADB with the Python standard library

#security #python #cryptography #devops

12 min read

Nikoloz Turazashvili (@axrisi)

Oct 21

Certificate authority keys: eMudhra's browser and runtime trust gap

#security #devops #python #programming

8 min read

Sam LABBE

Oct 22

A CA private key was the number 4. Your curl still trusts it (CVE-2026-111943)

#security #infosec #tls #pki

6 min read

frank chu

Oct 21

Eight CA private keys were integers under 256. I recovered all eight in 11 milliseconds.

#cybersecurity #infosec #security

6 min read

Anoymask

Oct 21

eMudhra: Eight Intermediate CA Private Keys Recoverable Due to Flawed Key Generation

#security #threatintel

9 min read

Kiell Tampubolon

Oct 24

The eMudhra CA Keys Were One Byte Long. Does Your Container Still Trust Them?

#security #devops #docker #linux

6 min read

Oct 21

Python requests and Node fetch still trusted eMudhra's compromised CAs on my machine. A 151-line check

#security #python #devops #webdev

8 min read

Oct 27

The eMudhra Certificate-Key Incident: Why Updating Windows May Not Update Your App

#security #cybersecurity

2 min read

Kiell Tampubolon

Oct 25

Kunci CA eMudhra Ternyata Cuma Satu Byte. Container Kamu Masih Percaya?

#security #tls #devops #indonesia

6 min read

Trend Analysis

Researchers discovered that eight eMudhra intermediate certificate authority private keys were generated with critically insufficient randomness, utilizing integers less than 256. This vulnerability allowed anyone to forge trusted HTTPS and code-signing certificates, prompting widespread security audits, browser patches, and updates to root trust stores across the industry.

Core Questions Under Debate:

How were eight intermediate CA private keys generated with single-byte entropy?
How can developers audit their software and local trust stores for compromised roots?
What improvements are needed in certificate authority key generation and root program auditing?

First detected: October 27, 2026

Last updated: about 3 hours ago

Algorithm: Vector Leader Clustering (threshold: 82%)

About this trend

This trend groups posts from the last 7 days that discuss similar concepts, technologies, or ideas.