<?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 Root CA - G1 - CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/products/emsign-root-ca---g1/</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 14:19:28 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/products/emsign-root-ca---g1/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 Intermediate Certificate Authority Compromise (CVE-2026-111943)</title><link>https://feed.craftedsignal.io/briefs/2026-10-emudhra-intermediate-ca-compromise/</link><pubDate>Wed, 21 Oct 2026 14:19:28 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-10-emudhra-intermediate-ca-compromise/</guid><description>The compromise of eight eMudhra intermediate certificate authority private keys due to a flawed key-generation process allows for the issuance of fraudulent, trusted certificates, necessitating urgent patches across programming language runtimes and browsers.</description><content:encoded><![CDATA[<p>On October 17, 2026, a security researcher identified that eight intermediate certificate authorities operated by eMudhra possessed insecurely generated private keys, which could be independently recovered. This compromise allows an attacker to issue fraudulent, trusted TLS and code-signing certificates. While there is no evidence of widespread abuse prior to defensive actions, the severity of the cryptographic failure prompted immediate revocation and denylisting efforts across browsers and language runtimes. The Go Project released CVE-2026-111943 to hardcode a denylist of the affected keys in the crypto/x509 library to protect applications that do not rely on system-level certificate revocation mechanisms.</p>
<h2 id="impact">Impact</h2>
<p>An attacker in possession of the compromised intermediate keys could potentially impersonate legitimate websites, intercept encrypted traffic, or sign malicious code. The risk is highest for applications that manage independent certificate bundles or runtimes that do not consume browser-based revocation lists like CRLSet or OneCRL.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Upgrade Go environments to version 1.26.10, 1.27.3, or later and rebuild all compiled applications to incorporate the new cryptographic denylist.</li>
<li>Update Firefox to version 158.0.1, ESR 115.43.1, or ESR 153.5.1 and ensure NSS is patched to 3.131.1 or later.</li>
<li>Audit and update software dependencies that maintain embedded certificate bundles, specifically Python's 'certifi' and Rust's 'webpki-roots' (ensure version 1.0.10 or newer).</li>
<li>Monitor certificate chain telemetry for the presence of the eight identified compromised intermediate CA public keys.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>vulnerability</category><category>browser</category><category>client-side</category><category>pki</category><category>certificate-authority</category><category>supply-chain</category><category>tls</category><category>infrastructure-security</category><category>informational</category><category>cryptography</category><category>web-security</category></item></channel></rss>