Published 19 November 2026 · Rathish Kumar, Invitty
If your website, VPN portal or any internal app uses an emSign SSL/TLS certificate from eMudhra, replace it now. Microsoft started removing the remaining eMudhra root certificates from Windows and Edge on 16 November 2026, and Apple stops trusting every certificate that chains to eMudhra's G1 hierarchy on 30 November 2026. eMudhra says its digital signature certificates (DSC) and eSign services are not affected.
What happened to eMudhra's certificate authority
On 17 October 2026 an independent researcher reported that the private keys of eight eMudhra intermediate certificate authorities were weak enough to be recovered. Six of those intermediates could issue TLS certificates and two could sign code. eMudhra traces the weak keys to a step in a key generation ceremony held on 30 April 2025, which means the problem sat unnoticed for about 18 months. It revoked all eight intermediates on 18 October.
eMudhra says no certificates were issued from the affected intermediates and that it has seen no evidence the keys were misused before disclosure. Browser makers acted anyway, because anyone holding those keys could have issued a certificate for any domain. Mozilla blocked them the same day, Chrome blocked the six TLS intermediates, and Apple added protections on 22 October. Microsoft updated its disallowed list on 20 October and pushed an out-of-band update on 26 October removing six emSign G3 roots and a cross-signed certificate. On 22 October eMudhra said it would wind down its publicly trusted TLS business and offered customers free migration, including Sectigo-issued certificates.
Which deadlines apply to your certificates?
The first wave hit the G3 hierarchy. The second wave, now under way, removes trust in eMudhra's remaining roots, including G1, the RSA hierarchy eMudhra moved its affected US customers onto. eMudhra says it had moved all its TLS customers outside the US to other options by 5 November. If nobody contacted you, check anyway, because certificates bought through resellers are easy to miss.
| Platform | Date | Effect |
|---|---|---|
| Chrome and Firefox | 16 November 2026 | G1-chained certificates issued after this date are not trusted; earlier ones still work there |
| Windows and Edge (Microsoft) | From 16 November 2026 | Remaining eMudhra roots, including emSign Root CA - G1, removed from the trusted root list as updates reach devices |
| Apple (macOS, iOS, Safari) | 30 November 2026 | All G1-chained certificates stop being trusted, whatever their issue date |
| Cisco IOS XR | 30 November 2026 (target) | Release 26.4.1 with the trust store fix |
| Cisco ISE | December 2026 to April 2027 (targets) | 3.5P5 in December; 3.3P13 and 3.4P8 later |
Read the Windows and Apple rows together. A certificate that still shows a green padlock in Chrome on your laptop can fail in Safari on a customer's iPhone in eleven days, and in Edge or a Windows app as soon as the root update lands. Waiting for the certificate's normal renewal date is not an option.
How to find emSign certificates in your environment
Start with anything public. For each website, VPN portal, mail server and API endpoint, open the certificate in a browser and read the issuer, or run openssl s_client -connect yourhost:443 -showcerts and look for "emSign" in the chain. Then check the places people forget:
- Firewall SSL VPN portals and the web admin pages of firewalls, switches and NAS boxes, where someone may have uploaded a bought certificate years ago.
- Load balancers, reverse proxies and Microsoft Exchange or IIS servers.
- Certificates bought through a reseller. The invoice may not say eMudhra, but the issuer field will.
- Code you signed with an emSign code signing certificate, if any.
Then look the other way: at what trusts eMudhra. Firewalls doing SSL inspection, Java applications, Linux servers and appliances keep their own certificate bundles and may still trust the compromised hierarchy until they are updated. Cisco's advisory, last revised on 16 November, lists dozens of affected products with fixes or target dates, and Red Hat is shipping trust store updates. Sophos published its own advisory on 27 October.
What it means for Indian businesses
The question we are getting most is about digital signature certificates for GST, MCA and income tax filings. eMudhra states that its DSC and eSign services are unaffected, in India or elsewhere. This incident concerns its publicly trusted SSL/TLS and code signing certificates, not the DSC tokens on your accountant's desk.
For SSL, eMudhra says migration to an alternate provider is free, and existing customers can request Sectigo-issued replacements through their CertiNext account or eMudhra support. Use that, but do not let the free route slow you down. If the replacement does not arrive this week, buying a new certificate for a public site is cheaper than a payment page that Safari refuses to load. Ask your supplier for a GST invoice in your company's name so the cost goes through cleanly.
Our view: treat this as a reminder to keep a simple certificate register, with host, issuer, expiry and owner. Most teams we meet only discover where their certificates live when one breaks.
Next step
Send us your domain list and the firewall or VPN models you run. We will check which hosts present emSign certificates, arrange replacements, and update the certificate on your firewall, VPN portal or mail server in one visit. If your firewall does SSL inspection, we will also confirm its trust store is current. See our firewall page and Cisco Secure Firewall for the appliances we support, or VAPT if you want a wider check of what is exposed.
Questions about the eMudhra certificate distrust
Is my eMudhra DSC for GST or MCA filing affected?
When will Apple stop trusting emSign certificates?
Do I have to pay for a replacement certificate?
Our firewall does SSL inspection. Does it need an update?
Not sure if your devices are affected? Send us the model and current firmware or version on WhatsApp, or use the form on this page. We will tell you whether this advisory applies to you and which update to schedule.
Sources
Facts in this post come from these pages, checked on 19 November 2026. Browser and vendor dates in incidents like this change, so check the latest version of each page.
- eMudhra: statement on the certificate security incident, with browser deadlines (updated 5 November 2026)
- Microsoft Security Response Center: response to compromised eMudhra CA keys (26 October 2026, updated 12 November 2026)
- Cisco informational advisory: emergency distrust of eMudhra root and intermediate CAs (version 1.12, 16 November 2026)
- Red Hat security bulletin RHSB-2026-012: eMudhra certificate compromise
- Sophos security advisories: eMudhra intermediate CA certificates compromised (27 October 2026)
- BleepingComputer: Mozilla, Google, Apple block compromised eMudhra CA certificates (20 October 2026)