Upcoming change for eMudhra CA certificates included in the Chrome Root Store
Comments on “Upcoming change for eMudhra CA certificates included in the Chrome Root Store”
Claim-checked. Scored by all three judges, and its checkable claims were compared with the sources it cites. How far stories are checked
Google's Chrome Root Program will stop trusting TLS server certificates chaining to eMudhra's emSign Root CA - G1 that were first logged after November 16, 2026, starting with Chrome 153, with a target date coinciding with Chrome 158 on November 17, 2026.
Why it ranked
No. 24 of 139 with a score of 0.70. The panel rated it highest on substantiated (0.81) and reader interest (0.78), lowest on technical depth (0.59). The judges disagreed most on new information (spread 0.48), so the story is marked contested. Placed No. 24, No. 16 by score alone: the seventh Security story of the day (−0.080). The placement terms move stories; they are not part of the score.
- AI judgeJudge 2claude-haiku-5-5
- Official Chrome Root Program notice on distrusting eMudhra CA after weak-key incident; concrete, security-relevant, actionable for certificate and TLS operators, though narrower in audience than landmark news.
- AI judgeJudge 3gpt-5.6-luna
- An authoritative Chrome Root Program notice sets a precise future trust cutoff for eMudhra’s remaining root after weak-key compromise. It is highly actionable for certificate operators and enterprises, with broad security implications but limited technical depth.
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.70total under rubric v2.3Contestedjudges differ by 0.48 on new information
- Significance0.69
- Reader interest0.78
- Audience breadth0.65
- Practical relevance0.72
- Substantiated0.81
- Technical depth0.59
- New information0.73
- Counts against: Promotional0.04
- Counts against: Overclaim0.10
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.70 | 0.62 | 0.74 | 0.69 | 0.12 | +0.24 | +0.165 |
| Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on? | 0.69 | 0.80 | 0.86 | 0.78 | 0.17 | +0.26 | +0.204 |
| Audience breadthHow many people who build technology does it concern? | 0.80 | 0.60 | 0.56 | 0.65 | 0.24 | +0.13 | +0.085 |
| Practical relevanceHow useful is it to someone who builds software or tech products? | 0.71 | 0.72 | 0.72 | 0.72 | 0.01 | +0.22 | +0.157 |
| 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.68 | 0.78 | 0.98 | 0.81 | 0.30 | +0.05 | +0.041 |
| Technical depthHow technically substantive is it? | 0.73 | 0.50 | 0.55 | 0.59 | 0.23 | +0.05 | +0.030 |
| New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)? | 0.82 | 0.45 | 0.93 | 0.73 | 0.48 , above the contested threshold | +0.05 | +0.037 |
| 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.09 | 0.02 | 0.01 | 0.04 | 0.08 | −0.19 | −0.008 |
| OverclaimDo the headline or conclusions claim more than the body supports? | 0.18 | 0.10 | 0.03 | 0.10 | 0.15 | −0.11 | −0.011 |
| Sum of contributions | +0.699 | ||||||
| Claim-check penalty | 0.000 | ||||||
| Total, as published | 0.699 | ||||||
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-11-05/24/"><img src="https://rubric.hrih.si/badge/2026-11-05/24.svg" alt="Ranked #24 on Rubric, 5 Nov 2026" width="238" height="28"></a>Claim check
Claim check: 4 matches source · 1 no source given · 3 couldn’t check. Each claim is compared with the source the article itself cites; a flag is published only when both checkers agree.
Matches sourceNumber
On October 17, 2026, a security researcher reported that eight eMudhra subordinate CA key pairs had been generated with near-zero entropy, making the private keys trivially recoverable.
The cited source says the same thing.
The article says “On October 17, 2026, a security researcher reported that eight eMudhra subordinate Certification Authority (CA) key pairs had been generated with near-zero entropy, resulting in trivially recoverable private keys”
The source says “On Saturday, October 17, 2026, at 18:05 UTC, the Chrome Root Program received a report from a security researcher regarding the compromise of private keys associated with eight eMudhra subordinate…”
Source cited by the article: blog.google/security/protecting-chrome-and-android-users-from-compromised-emudhra-intermediate-ca-certificates
Couldn’t checkVersion
Chrome blocked the affected TLS intermediate CA keys via CRLSet and removed the emSign ECC Root CA - G3 in Chrome Root Store Version 43.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “blocking the affected Transport Layer Security (TLS) intermediate CA keys via CRLSet and subsequently removing CN=emSign ECC Root CA - G3, OU=emSign PKI, O=eMudhra Technologies Limited, C=IN in Chrome Root…”
The source says No passage could be compared.
Source cited by the article: crt.sh
Matches sourceQuote
eMudhra announced its decision to withdraw from the global SSL/TLS certificate business and transition its customers to other CAs.
The cited source says the same thing.
The article says “eMudhra announced its decision to withdraw from the global SSL/TLS certificate business and transition its customers to other CAs”
The source says “its Board has decided to voluntarily withdraw from the global SSL/TLS certificate business”
Source cited by the article: emudhra.com/en/press-release/emudhra-to-exit-global-ssl-tls-certificate-business
Matches sourceNumber
The Chrome Root Program, other root store operators and members of the public have asked eMudhra for additional details about its key generation and management practices.
The cited source says the same thing.
The article says “the Chrome Root Program, other root store operators, and members of the public have asked eMudhra for additional details regarding its key generation and management practices”
The source says “We request that eMudhra answer the following questions to help us (and others) better understand the situation and more effectively plan next steps to protect our user communities”
Source cited by the article: bugzilla.mozilla.org/show_bug.cgi
Matches sourceGeneralization
eMudhra has not responded to inquiries about its key-handling practices in a way that meets Chrome's expectations or convincingly shows the risk does not extend beyond the known weak CA keys.
The cited source says the same thing.
The article says “it has not affirmatively responded to inquiries regarding its key-handling practices in a manner consistent with our expectations”
The source says “Comment 43 does not answer Mozilla's questions or Chrome's Q1–Q12 ( comment 30 ), which fall due under that rule on 28 October”
Source cited by the article: bugzilla.mozilla.org/show_bug.cgi
Couldn’t checkVersion
TLS server authentication certificates chaining to emSign Root CA - G1 whose earliest SCT is dated after November 16, 2026 11:59:59 PM UTC will no longer be trusted by default in Chrome 153 and higher.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “whose earliest Signed Certificate Timestamp (SCT) is dated after November 16, 2026 11:59:59 PM UTC, will no longer be trusted by default in Chrome 153 and higher”
The source says No passage could be compared.
Source cited by the article: crt.sh
No source givenDate
The change aims to coincide with the Chrome 158 Stable release on November 17, 2026.
The article gives no link or citation for it.
The article says “This change aims to coincide with the Chrome 158 Stable release on November 17, 2026”
The source says No source to compare with.
Couldn’t checkCausal conclusion
If a user or enterprise explicitly trusts the certificate on a platform relying on the Chrome Root Store, the SCT-based constraints are overridden and certificates function as they do today.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “the SCT-based constraints described above will be overridden and certificates will function as they do today”
The source says No passage could be compared.
Source cited by the article: chromium.googlesource.com/chromium/src/+/main/net/data/ssl/chrome_root_store/faq.md
Also covered by
No other coverage was clustered with this story.
Elsewhere
Elsewhere: HN 9 pts, not on front page
Recorded for context only, checked 5 Nov 2026, 05:46 UTC. It played no part in the ranking.