<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/emudhra-intermediate-ca-compromise-noemyuyli" -->

---
title: eMudhra intermediate CA compromise | daily.dev
description: Mozilla received a report that private keys tied to eight eMudhra intermediate certificates have been compromised, which could let attackers issue fraudulent...
canonical: https://daily.dev/posts/emudhra-intermediate-ca-compromise-noemyuyli
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: eMudhra intermediate CA compromise | daily.dev
og:description: Mozilla received a report that private keys tied to eight eMudhra intermediate certificates have been compromised, which could let attackers issue fraudulent...
og:url: https://daily.dev/posts/emudhra-intermediate-ca-compromise-noemyuyli
og:image: https://api.daily.dev/og/posts/NoEmyUyLI.png
og:image:alt: eMudhra intermediate CA compromise
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# eMudhra intermediate CA compromise

**[LWN.net](https://daily.dev/sources/lwn)** · 1 min read · 0 upvotes · 0 comments

## Summary

Mozilla received a report that private keys tied to eight eMudhra intermediate certificates have been compromised, which could let attackers issue fraudulent HTTPS certificates for websites they don't control. Mozilla blocked the affected certificates via its OneCRL revocation list and updated trust settings in NSS 3.131.1. According to a single-page site, Chrome blocked them starting October 17, Apple devices on the 19th, and Microsoft on the 20th. The NetBSD foundation issued instructions for blocking the certificates on NetBSD installations, and users of other browsers or OSes may wish to check for similar guidance.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://lwn.net/Articles/1101643>

## Questions this post answers

### What happened with the eMudhra intermediate CA key compromise?

Private keys associated with eight eMudhra intermediate certificates were compromised, which could let attackers issue fraudulent HTTPS certificates for websites they don't control and intercept or modify traffic. Mozilla blocked the affected certificates using its OneCRL centralized revocation list and updated NSS to version 3.131.1 to remove trust in them.

_Track how browser vendors respond to CA compromises like this on daily.dev to keep your trust store decisions current._

### When did major browsers block the compromised eMudhra certificates?

Chrome blocked the compromised eMudhra certificates starting October 17, Apple devices followed on October 19, and Microsoft blocked them on October 20. Mozilla also blocked them via OneCRL and shipped NSS 3.131.1 with updated trust settings. NetBSD separately published instructions for blocking the certificates on its systems.

_Developers auditing TLS trust across platforms can follow rollout timelines like this one on daily.dev._

## Similar posts on daily.dev

- [Web PKI Ditches TLS Client Authentication](https://daily.dev/posts/web-pki-ditches-tls-client-authentication-o830n7oou) · Feisty Duck · 0 upvotes · 0 comments
- [The Morning After We Pull a Root of Trust, Nobody Owns It](https://daily.dev/posts/the-morning-after-we-pull-a-root-of-trust-nobody-owns-it-xssy4h4f3) · Dark Reading · 0 upvotes · 0 comments
- [Changes to TLS clientAuth Certificates: Ensuring You’re Not Impacted](https://daily.dev/posts/changes-to-tls-clientauth-certificates-ensuring-you-re-not-impacted-ebetmr0aj) · Cisco · 0 upvotes · 0 comments

---

Tags: [#firefox](https://daily.dev/tags/firefox)

[View this post on daily.dev](https://daily.dev/posts/emudhra-intermediate-ca-compromise-noemyuyli)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"eMudhra intermediate CA compromise","url":"https://daily.dev/posts/emudhra-intermediate-ca-compromise-noemyuyli","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/emudhra-intermediate-ca-compromise-noemyuyli"},"datePublished":"2026-10-20T15:00:20.280Z","dateModified":"2026-10-21T04:52:44.852Z","description":"Mozilla received a report that private keys tied to eight eMudhra intermediate certificates have been compromised, which could let attackers issue fraudulent...","image":"https://media.daily.dev/image/upload/s--qPvKM23u--/f_auto/v1722860399/public/Placeholder%2009","thumbnailUrl":"https://media.daily.dev/image/upload/s--qPvKM23u--/f_auto/v1722860399/public/Placeholder%2009","isAccessibleForFree":true,"articleSection":"LWN.net","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"LWN.net","logo":"https://media.daily.dev/image/upload/s--4jjE7GIK--/f_auto,q_auto/v1774960833/logos/lwn?_a=BAMAMiWQ0","url":"https://daily.dev/sources/lwn"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/emudhra-intermediate-ca-compromise-noemyuyli","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"firefox","timeRequired":"PT1M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"LWN.net","item":"https://daily.dev/sources/lwn"},{"@type":"ListItem","position":3,"name":"eMudhra intermediate CA compromise"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/emudhra-intermediate-ca-compromise-noemyuyli#faq","mainEntity":[{"@type":"Question","name":"What happened with the eMudhra intermediate CA key compromise?","acceptedAnswer":{"@type":"Answer","text":"Private keys associated with eight eMudhra intermediate certificates were compromised, which could let attackers issue fraudulent HTTPS certificates for websites they don't control and intercept or modify traffic. Mozilla blocked the affected certificates using its OneCRL centralized revocation list and updated NSS to version 3.131.1 to remove trust in them. Track how browser vendors respond to CA compromises like this on daily.dev to keep your trust store decisions current."}},{"@type":"Question","name":"When did major browsers block the compromised eMudhra certificates?","acceptedAnswer":{"@type":"Answer","text":"Chrome blocked the compromised eMudhra certificates starting October 17, Apple devices followed on October 19, and Microsoft blocked them on October 20. Mozilla also blocked them via OneCRL and shipped NSS 3.131.1 with updated trust settings. NetBSD separately published instructions for blocking the certificates on its systems. Developers auditing TLS trust across platforms can follow rollout timelines like this one on daily.dev."}}]}
```

