<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:webfeeds="http://webfeeds.org/rss/1.0"><channel><title>EmSign Intermediate CA Certificates - CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/products/emsign-intermediate-ca-certificates/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata. Fed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Wed, 21 Oct 2026 07:47:00 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/products/emsign-intermediate-ca-certificates/feed.xml" rel="self" type="application/rss+xml"/><image><url>https://feed.craftedsignal.io/favicon-32x32.png</url><title>CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/</link><width>32</width><height>32</height></image><webfeeds:icon>https://feed.craftedsignal.io/favicon.svg</webfeeds:icon><item><title>eMudhra: Eight compromised intermediate CA keys threaten TLS trust</title><link>https://feed.craftedsignal.io/briefs/2026-10-emudhra-intermediate-key-compromise/</link><pubDate>Wed, 21 Oct 2026 07:47:00 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-10-emudhra-intermediate-key-compromise/</guid><description>Eight eMudhra intermediate CA private keys were compromised. A researcher found one key had the integer value 4; Mozilla blocked the affected certificates and updated its trust store.</description><content:encoded><![CDATA[<p>Mozilla received a report on 17 October 2026 that private keys for eight eMudhra intermediate CA certificates had been compromised. Security researcher Scott Helme independently recovered the weak keys from the public certificates and reported that one private key was the integer <strong>4</strong>; others included <strong>56</strong> and <strong>115</strong>. This describes a very small key value, not a four-byte certificate. A holder of a compromised CA key could issue fraudulent HTTPS certificates. Intercepting a connection would also require an on-path position. The cited sources do not establish observed malicious use of these keys.</p>
<h2 id="affected-intermediate-cas">Affected intermediate CAs</h2>
<p>Mozilla's <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=2083449">incident record</a> identifies six TLS issuers and two code-signing issuers. The names and CCADB identifiers are:</p>
<table>
	<thead>
			<tr>
					<th>Purpose</th>
					<th>Intermediate CA</th>
					<th>CCADB ID</th>
			</tr>
	</thead>
	<tbody>
			<tr>
					<td>TLS</td>
					<td>EM EV TLS CA - G3B (eMudhra BV)</td>
					<td>A012304</td>
			</tr>
			<tr>
					<td>TLS</td>
					<td>EM OV TLS CA - G3B (eMudhra BV)</td>
					<td>A012308</td>
			</tr>
			<tr>
					<td>TLS</td>
					<td>EM DV TLS CA - G3B (eMudhra BV)</td>
					<td>A012302</td>
			</tr>
			<tr>
					<td>TLS</td>
					<td>EM EV TLS CA - G3C (eMudhra Inc)</td>
					<td>A012296</td>
			</tr>
			<tr>
					<td>TLS</td>
					<td>EM OV TLS CA - G3C (eMudhra Inc)</td>
					<td>A012300</td>
			</tr>
			<tr>
					<td>TLS</td>
					<td>EM DV TLS CA - G3C (eMudhra Inc)</td>
					<td>A012294</td>
			</tr>
			<tr>
					<td>Code signing</td>
					<td>EM OV CS CA - G3B (eMudhra BV)</td>
					<td>A012306</td>
			</tr>
			<tr>
					<td>Code signing</td>
					<td>EM OV CS CA - G3C (eMudhra Inc)</td>
					<td>A012298</td>
			</tr>
	</tbody>
</table>
<p>Use the SHA-256 certificate fingerprints in Mozilla's incident record when matching a certificate chain; a CA name alone is not a reliable cryptographic identifier.</p>
<p>Mozilla blocked the affected certificates through Firefox OneCRL on 17 October and released Firefox and NSS updates for clients that may not receive that block. The certifi maintainer removed the affected emSign roots from its CA bundle in version 2026.10.18.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Check which browsers, libraries, containers, and custom trust stores still trust the affected certificate chain.</li>
<li>Apply current browser and NSS updates; update affected certifi installations to 2026.10.18 or later and rebuild bundled images.</li>
<li>Investigate any suspicious TLS certificate chains issued through the affected intermediates, while keeping observed exploitation separate from the confirmed key compromise.</li>
</ul>
]]></content:encoded><category domain="severity">critical</category><category domain="type">advisory</category><category>certificate-authority</category><category>tls-interception</category></item></channel></rss>