|
View in browser
|
|
Triangulate BRIEF
Actionable insights on India’s tech policy
|
eMudhra’s weak keys: check your certificates now
- A researcher reported the weak keys on 17 October 2026.
- This is an incident, not a new rule. The duties that apply were already in force.
|
|
What happened Fact
- A certificate authority (CA) vouches that a website is genuine, which is what the browser padlock shows. Eight of eMudhra’s intermediate CAs, which sign for a trusted root, had private keys weak enough to recover, so an attacker could have issued fake website certificates.
- Chrome and Firefox blocked six of them within hours of the report. eMudhra says it revoked all eight on 18 October.
- Browsers then began removing the root itself, emSign ECC Root CA – G3 (Mozilla from 20 October, Microsoft on 26 and 27 October, Chrome due 27 October), so any certificate chaining to it can fail. Google and Microsoft are reviewing eMudhra’s other roots.
- Accounts differ. eMudhra says all eight were TLS (website) intermediates and that it knows of no evidence anyone recovered or used the keys. CERT-In names six TLS ones, warns about code-signing chains and says exploitation was unconfirmed by 21 October. Mozilla calls the keys compromised.
|
|
|
Part 1 of 2
Triangulated
Law. Economics. Business.
|
|
|
Law Fact: which rules apply, and which do not
- CERT-In’s Directions of 28 April 2022 already require organisations to report listed incidents within 6 hours of noticing them (Direction (ii)) and keep logs for 180 days in India (Direction (iv)). The list includes spoofing and phishing, and attacks on applications.
- CERT-In’s advisory CIAD-2026-0050 (21 October) recommends checks and replacement but sets no deadline. MeitY formed a special team, in a statement reported on 21 and 22 October.
- The Controller of Certifying Authorities licenses eMudhra’s Digital Signature Certificates (DSC) and eSign, which MeitY says are unaffected. The failed part, global website certificates, runs under browser root programmes and independent audits that MeitY says it is not involved in. We found no Indian rule that governs it.
|
|
|
Economics Who bears the cost: fact first, then analysis
- eMudhra says global website certificates are about 1% of its revenue. On 22 October its board decided to exit that business, with no exit date. On 23 October ICRA kept its A (Stable) rating, citing reputational damage and regulatory uncertainty.
- eMudhra offers replacement certificates at no charge and says most customers have moved. Chrome counted about 30,800 unexpired certificates under the root on 21 October, about 99.9% of them via InCommon, a US university service. That suggests few Indian sites sat under it.
- Our view: eMudhra bears the main cost. For most Indian companies the bill is small, but a firm that cannot list its certificates in a day pays in engineer time and outage risk. A tested second CA costs little next to an emergency swap.
|
|
|
Business Who gains and loses: fact, then analysis
- In the week of 19 October eMudhra’s shares fell about 36%, from about ₹540 to ₹345.60. Sectigo, another CA, revoked its cross-signing for eMudhra on 19 October and says its own certificates are unaffected. eMudhra says the flaw went unnoticed for about 18 months and two audits.
- Our view: the failed business sat outside Indian licensing, so browsers acted within hours and the Indian response came days later. Demand moves to other CAs, and customers, banks and investors will ask suppliers for a certificate list and a backup CA. Buyers may not separate DSC and eSign, which MeitY says are unaffected, from the failed business. An audited CA is where diligence starts, not ends.
|
|
|
Part 2 of 2
Actionable Next Steps
By role.
|
|
| Forward this to whoever owns each action. |
Required = the law Recommended = our advice |
For Founders and CEOs
Recommended Now
Ask your security or engineering lead which of your systems use or trust an eMudhra certificate.
Done looks like: a written reply listing the systems, or saying none were found.
Recommended By 13 Nov 2026
Write a three-line customer statement: whether you were affected, what you checked, and when.
Done looks like: three lines, approved by your security lead, ready to send.
Recommended By 30 Nov 2026
Name an owner for your certificate list and renewals, and approve a second CA as backup.
Done looks like: one named person, a budget line, and a second CA approved.
|
|
For Legal Teams
Required CERT-In Direction (ii) · within 6 hours of noticing
Report any Annexure I incident (it includes spoofing and phishing, and attacks on applications) to CERT-In within 6 hours of noticing it, and name who files, with a deputy.
Done looks like: a one-page procedure naming the filer and deputy, with one drill run.
Recommended By 13 Nov 2026
Review contracts with certificate vendors and customers. Mark the notice, replacement and liability clauses and any security warranty.
Done looks like: a list of contracts reviewed, with those clauses marked.
Recommended By 20 Nov 2026
If RBI, SEBI, IRDAI or another sector regulator oversees you, compare its incident-reporting window with CERT-In’s 6 hours.
Done looks like: a one-page table of each reporting window, who files, and where.
|
|
For Product and Operations Teams
Required CERT-In Direction (iv) · already in force
Keep logs of all your ICT systems, securely and in India, for a rolling 180 days.
Done looks like: web-server, proxy and certificate-system logs go back 180 days and sit in India.
Recommended Now
Check every public hostname’s certificate chain for emSign or eMudhra, and replace any chain ending at emSign ECC Root CA – G3. Search Certificate Transparency logs (public records of issued certificates, at crt.sh) for certificates you did not request.
Done looks like: a hostname list with issuers, no chain ending at that root, and a dated log search.
Recommended By 13 Nov 2026
Check trust stores outside browsers (Java keystores, container images, proxies, appliances, embedded devices) and apply vendor updates that block the eight CAs or remove the G3 root (Microsoft shipped Windows updates on 26 October). If you ship signed software, check your code-signing chain too.
Done looks like: each host, image and appliance is listed, with the eight CAs blocked or confirmed absent.
Recommended By 31 Jan 2027
Automate certificate renewal (ACME is the standard way) and set up a second CA, so the next distrust event takes hours, not weeks.
Done looks like: a second CA configured and tested on one low-risk domain, with renewals automatic.
|
|
For Investors
Recommended Now
Ask each portfolio company whether any system uses or trusts an eMudhra certificate, and who owns its certificate list. Set a reply date.
Done looks like: a reply from every company by your date.
Recommended Next diligence round
Add three certificate questions to diligence: do you keep a full certificate list, which CAs do you rely on, and have you tested a backup?
Done looks like: the questions sit in your checklist, with answers on file.
Recommended Ongoing
Track three open items, none with a published date: eMudhra’s root-cause report to the browsers’ CA database (CCADB), with KPMG reviewing; Google’s and Microsoft’s decisions on its other roots; and MeitY’s probe.
Done looks like: each item sits in your calendar with an owner.
|
|
|
Send feedback, corrections or compliments.
|
| Know someone who should read this? Forward this email, or send them to triangulatepolicy.com. |
|
Triangulate Tech Policy
Official sources:
CERT-In advisory CIAD-2026-0050, 21 October 2026 ·
CERT-In Directions, 28 April 2022 ·
Mozilla security blog, 20 October 2026 ·
Google security blog ·
eMudhra statement ·
MeitY statement (AIR report, 22 October 2026). This is general information, not legal advice.
Verified on: 31 October 2026, against the CERT-In advisory and Directions and the published statements of Mozilla, Google, eMudhra and MeitY. Share prices, certificate counts, the Apple, Microsoft and ICRA items and the board’s decision date come from secondary reports.
Follow Triangulate: LinkedIn · Medium
Partner with us: See how to partner with Triangulate
You are receiving this because you subscribed at triangulatepolicy.com.
Unsubscribe |
triangulatepolicy.com |
editor@triangulatepolicy.com
|
|
|