4 real? Tracking exploitation and patching of eMudhra’s weak keys
Comments on “4 real? Tracking exploitation and patching of eMudhra’s weak keys”
Claim-checked. Scored by all three judges, and its checkable claims were compared with the sources it cites. How far stories are checked
Cloudflare reports that eMudhra's intermediate CA keys were trivially weak (one was the number 4), so anyone can derive them and forge certificates for any domain that unpatched clients accept. Its outbound logging saw about 22,000 handshakes using the keys in a week, mostly test sites, and no evidence of interception, though forged certificates appeared within hours of disclosure. Probes on challenge pages, skewed by bot traffic, show over half of large networks still trusting the chain. Figures come from Cloudflare alone, and eMudhra's script explanation is unverified.
Why it ranked
No. 1 of 111 with a score of 0.78. The panel rated it highest on substantiated (0.88) and practical relevance (0.86), lowest on significance (0.77). Placed No. 1, where the score alone would also have put it: close to “Our Response To The eMudhra Key Disclosure Incident”, No. 1 on Tuesday 27 October 2026 (−0.008). The placement terms move stories; they are not part of the score.
- AI judgeJudge 2claude-haiku-5-5
- Detailed, data-backed incident follow-up on a compromised CA with weak keys; major security impact and actionable patching guidance for builders, with substantial technical detail and largely unique information.
- AI judgeJudge 3gpt-5.6-luna
- A detailed primary-source incident follow-up quantifies exploitation attempts, patching, vulnerable clients, and remediation. It is highly actionable for security and infrastructure builders, with strong evidence and only minor corporate framing.
Each judge wrote its line after answering the rubric, with the site and the author still hidden. Every answer behind this is in the table under Score.
Score
0.78total under rubric v2.3
- Significance0.77
- Reader interest0.84
- Audience breadth0.82
- Practical relevance0.86
- Substantiated0.88
- Technical depth0.81
- New information0.78
- Counts against: Promotional0.08
- Counts against: Overclaim0.23
Each judge’s answer per question (0–1), their mean and spread, and what the question adds to the score (weight × mean).
| Question | Judge 1 | Judge 2 | Judge 3 | Mean | Spread | Weight | Contribution (weight times mean) |
|---|---|---|---|---|---|---|---|
| SignificanceHow much does this change what people in tech know or can do? | 0.78 | 0.72 | 0.82 | 0.77 | 0.10 | +0.24 | +0.185 |
| Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on? | 0.77 | 0.80 | 0.95 | 0.84 | 0.18 | +0.26 | +0.218 |
| Audience breadthHow many people who build technology does it concern? | 0.88 | 0.80 | 0.78 | 0.82 | 0.10 | +0.13 | +0.107 |
| Practical relevanceHow useful is it to someone who builds software or tech products? | 0.86 | 0.85 | 0.88 | 0.86 | 0.03 | +0.22 | +0.190 |
| SubstantiatedHow well is it backed? Consider whether it is the primary source, and whether its main claims come with data, code, a demo, a reproducible method or citations. | 0.86 | 0.85 | 0.92 | 0.88 | 0.07 | +0.05 | +0.044 |
| Technical depthHow technically substantive is it? | 0.86 | 0.80 | 0.78 | 0.81 | 0.08 | +0.05 | +0.041 |
| New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)? | 0.74 | 0.75 | 0.86 | 0.78 | 0.12 | +0.05 | +0.039 |
| PromotionalIs it mainly marketing with little substance (a press release, ad or sponsored post with no real information)? A launch post that carries real news is not promotional. | 0.06 | 0.10 | 0.08 | 0.08 | 0.04 | −0.19 | −0.015 |
| OverclaimDo the headline or conclusions claim more than the body supports? | 0.42 | 0.15 | 0.12 | 0.23 | 0.30 | −0.11 | −0.025 |
| Sum of contributions | +0.783 | ||||||
| Claim-check penalty | 0.000 | ||||||
| Total, as published | 0.783 | ||||||
Spread is the highest minus the lowest judge answer. marks a spread above 0.40: the judges disagree, and the story is marked contested.
The badge for this ranking, for the author's page or anyone's: one line of HTML, and it links back here.
<a href="https://rubric.hrih.si/editions/2026-10-31/1/"><img src="https://rubric.hrih.si/badge/2026-10-31/1.svg" alt="Ranked #1 on Rubric, 31 Oct 2026" width="238" height="28"></a>Claim check
Claim check: 7 no source given · 1 couldn’t check. Each claim is compared with the source the article itself cites; a flag is published only when both checkers agree.
No source givenNumber
eMudhra used the number 4 as one of eight weak keys, with the other seven being 56, 66, 115, 155, 156, 230 and 237.
The article gives no link or citation for it.
The article says “they picked the number 4. Not even four digits, just the number 4. The other seven keys were similarly weak: 56, 66, 115, 155, 156, 230 and 237”
The source says No source to compare with.
No source givenFirst, only or fastest
A certificate authority with weak keys this serious is unprecedented, unlike earlier compromised CAs such as DigiNotar, TÜRKTRUST and TrustWave, where key access was contained.
The article gives no link or citation for it.
The article says “A certificate authority (CA) with weak keys this serious is unprecedented, and the potential consequences are significant”
The source says No source to compare with.
Couldn’t checkQuote
eMudhra announced it is exiting the public CA business and attributed the problem to a mistake in a key generation script.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “eMudhra announced they’re exiting the public CA business and have claimed a mistake in a key generation script, but have not yet shared the script”
The source says No passage could be compared.
Source cited by the article: arstechnica.com/security/2026/10/disgraced-emudhra-drops-out-of-tls-business-following-certificate-debacle
No source givenNumber
Cloudflare's AI-assisted source code analysis to find all systems trusting the weak keys produced a full analysis within four hours.
The article gives no link or citation for it.
The article says “we started an AI-assisted analysis of our source code to find all other systems that trust these weak keys. Within four hours we had a full analysis”
The source says No source to compare with.
No source givenNumber
Cloudflare saw about 22,000 attempted handshakes with the weak eMudhra keys in the week after logging rolled out, two-thirds of them to test sites.
The article gives no link or citation for it.
The article says “we’ve seen about 22,000 attempted handshakes with the weak eMudhra keys. Two-thirds of the attempts were fetches of test sites”
The source says No source to compare with.
No source givenCausal conclusion
One forged certificate was dated October 20 at 18:19 UTC, less than an hour after Mozilla's bug report was made public, showing forging within hours of disclosure.
The article gives no link or citation for it.
The article says “these keys appear to have been used to forge certificates within hours of the weakness becoming public: one of the forged certificates we saw was dated October 20 at 18:19…”
The source says No source to compare with.
No source givenGeneralization
Cloudflare found no evidence that the weak keys were used to intercept its connections.
The article gives no link or citation for it.
The article says “there is no evidence of the weak keys being used to intercept Cloudflare's connections so far”
The source says No source to compare with.
No source givenNumber
Across large networks, more than half of probes still accept the compromised chain, and embedded browsers like Android WebView show 30–40% still accepting.
The article gives no link or citation for it.
The article says “Across the large networks, more than half of probes still accept the compromised chain”
The source says No source to compare with.
Also covered by
No other coverage was clustered with this story.
Elsewhere
Elsewhere: HN 11 pts, not on front page
Recorded for context only, checked 31 Oct 2026, 05:46 UTC. It played no part in the ranking.