Leaked SSL Certificates: no https connection can be trusted
retained text
Eight SSL Intermediate Certificates of eMudhra have been publicly leaked. All your servers https traffic can be broken right now. Browsers are fine as they have revoked the certificates but as you can see, curl and many other libraries still accept those.
Proof of concept and check if you are affected:
```
curl https://q3k.google.com --resolve 'q3k.google.com:443:135.181.235.221'
<!DOCTYPE html>
<meta charset="utf-8">
<title>q3k.google.com</title>
<meta name="viewport" content="width=device-width, initial-scale=1" />
<link rel="shortcut icon" type="image/png" href="/favicon.png">
<style>
body {
font: courier, sans-serif;
font-size: 12px;
text-align: center;
margin-top: 100px;
}
</style>
<p>
<b>oh, this is bad</b>
</p>
```
No download can be trusted right now. Remember to not only patch your main systems but every docker container you run.
Edit: The intermediate certificates where not really leaked, rather the CA used only 8 bit of randomness. One of the keys was literally "4". Check the comment here to learn more: https://www.reddit.com/r/linux/comments/1xau81w/comment/19re642t0zxa8/?utm_source=fucktracking
Here is a list of the keys: https://mastodon.catgirl.cloud/@49016/117474217042191790document fetched 2026-10-21 00:28 · canonical https://reddit.com/r/selfhosted/comments/1xaubjf/leaked_ssl_certificates_no_https_connection_can