CTIPilot
AI-generated · no human review · verify critical claims against the linked source. how it works →

Oracle Global Lifecycle Management OPatch

product · product:oracle-global-lifecycle-management-opatch

Coverage
1
first 2026-10-21 → last 2026-11-15
Latest activity
2026-11-12
eMudhra: eight ECDSA CA keys guessable, eight RSA CAs revoked; Windows drops the rest 2026-11-16; update…
Peak priority
notable
1 notable
Targets
·
no sector or region stated
Sources cited
27
22 hosts

Action items (3)

Do-now tasks recorded on the entries about Oracle Global Lifecycle Management OPatch, newest first. Check the date before acting on an older one.

  • Update every non-browser TLS client that keeps its own CA bundle or does not check revocation to a fixed version: standalone Java runtimes, including those already updated on 2026-10-21, to the update of Oracle's Security Alert CVE-2026-114820 or OpenJDK (Oracle Database Server, Autonomous Health Framework and OPatch installations too), Python 3.15.2, 3.14.10, 3.13.18, 3.12.16 or 3.11.18 together with pip 26.2.2 or later, Go 1.27.3 or 1.26.10, self-managed GitLab to a fixed patch release together with GitLab Runner 19.5.1, and SonicWall Gen7 firewalls with Client DPI-SSL enabled to SonicOS 7.3.4-7015 or later and Gen8 to 8.2.3-8015 or later; then confirm with curl against the incident tracker's test host that the client rejects the certificate; on managed Macs update to macOS 27.2.1, 26.7.3 or 15.8.3, or where that is not possible remove emSign ECC Root CA - G3 from /etc/ssl/cert.pem as Apple describes (AAA Certificate Services is optional and can stop tools that read only that file from verifying some unaffected sites).
    2026-10-21CVE-2026-91403 +3
  • Replace, by hand where the ACME client does not support ACME Renewal Information, every TLS certificate your organisation holds that chains to emSign ECC Root CA - G3 or to another of the seven certificates Microsoft removed from the Windows and Edge trust lists, or that was issued by one of the eight RSA G2B and G2C issuing CAs eMudhra revoked on 2026-11-07, because Chrome's removal of the G3 root was due on 2026-10-27 and the Windows change takes effect when the trust-list update reaches a device; deliver the updated Disallowed Certificate Trust List and the trust-list changes Microsoft describes, including its out-of-band update of 2026-10-26, to Windows devices that do not receive automatic certificate-trust updates; do not renew or reissue under emSign Root CA - G1 after 2026-11-16, because Chrome 153 and higher will not trust by default a certificate under it whose earliest SCT is later, and Windows, Edge and WebView2 stop trusting the remaining eMudhra roots on 2026-11-16 as Microsoft's update of 2026-11-10 describes.
    2026-10-21CVE-2026-91403 +3
  • Apply Cisco's remediation now for the products its eMudhra advisory (version 1.11) lists with a fix or a procedure available: the CA-trust distrust guide for IOS XE and the guidance for Secure Firewall ASA, FTD and FMC, Secure Email Gateway and Secure Email and Web Manager (run the updatenow command where updates are manual), Duo Access Gateway 3.2.0, Duo Network Gateway 3.4.1, Duo Agentic Authorization Connector 1.0.1 and ThousandEyes Enterprise Agent (Application-hosting Agent 5.2.2).
    2026-10-21CVE-2026-91403 +3

Defender insights

What each entry about Oracle Global Lifecycle Management OPatch tells a defender to do, newest first.

2026-10-21NOTABLEeMudhra: eight ECDSA CA keys guessable, eight RSA CAs revoked; Windows drops the rest 2026-11-16; update clients

Exposure · triage · detection

Story timeline

  1. 2026-10-21eMudhra: the private keys of eight ECDSA intermediate CA certificates were trivially recoverable, so anyone could forge trusted HTTPS certificates, and eight RSA intermediates were revoked on 2026-11-07 for key handling eMudhra cannot show compliant; browsers block the eight ECDSA intermediates, clients with their own trust store or no revocation checking need an update (CVE-2026-111943 in Go)
    active-threatseMudhra: eight ECDSA CA keys guessable, eight RSA CAs revoked; Windows drops the rest 2026-11-16; update clients

Hunting pivots

Releases covered
Oracle Global Lifecycle Management OPatch
ATT&CK techniques (1 across 2 tactics)

1 technique observed across 1 entry about this entity, derived from entry metadata and body evidence, never asserted without a published entry behind it · pinned to MITRE ATT&CK v20.1 · compare on the matrix · Navigator layer (JSON)

  • Credential AccessAdversary-in-the-Middle
  • CollectionAdversary-in-the-Middle

Credential Access TA0006

T1557Adversary-in-the-Middle×1

Adversaries may attempt to position themselves between two or more networked devices using an adversary-in-the-middle (AiTM) technique to support follow-on behaviors such as Network Sniffing, Transmitted Data Manipulation, or replay attacks (Exploitation for Credential Access). By abusing features of common networking protocols that can determine the flow of network traffic (e.g. ARP, DNS, LLMNR, etc.), adversaries may force a device to communicate through an adversary controlled system so they can collect information or perform additional actions.

Evidence: 2026-10-21/emudhra-intermediate-ca-keys-recoverable-trust-store-updates · ATT&CK page ↗

Collection TA0009

T1557Adversary-in-the-Middle×1

Adversaries may attempt to position themselves between two or more networked devices using an adversary-in-the-middle (AiTM) technique to support follow-on behaviors such as Network Sniffing, Transmitted Data Manipulation, or replay attacks (Exploitation for Credential Access). By abusing features of common networking protocols that can determine the flow of network traffic (e.g. ARP, DNS, LLMNR, etc.), adversaries may force a device to communicate through an adversary controlled system so they can collect information or perform additional actions.

Evidence: 2026-10-21/emudhra-intermediate-ca-keys-recoverable-trust-store-updates · ATT&CK page ↗

Entries about Oracle Global Lifecycle Management OPatch (1)

2026-10-21 · view entry permalink →

NOTABLECVE-2026-91403 +3updatedNATOA1

eMudhra: the private keys of eight ECDSA intermediate CA certificates were trivially recoverable, so anyone could forge trusted HTTPS certificates, and eight RSA intermediates were revoked on 2026-11-07 for key handling eMudhra cannot show compliant; browsers block the eight ECDSA intermediates, clients with their own trust store or no revocation checking need an update (CVE-2026-111943 in Go)

On 2026-10-17 a researcher reported to the Chrome Root Program, and Mozilla received a report the same day, that the private keys of eight eMudhra subordinate CA certificates were compromised: the keys were so weak that anyone could forge trusted HTTPS certificates to impersonate any website against clients that have not removed trust in those CAs; Google describes the cause as insufficient randomness (Google, 2026-10-20; Mozilla, 2026-10-20). BleepingComputer, citing Mozilla's incident report, says all eight were P-384 keys generated in April 2025 with values below 256, so testing 256 numbers recovers a key (BleepingComputer, 2026-10-20). eMudhra's incident report of 2026-11-10 says the keys were generated correctly on its hardware module at a ceremony on 2025-04-30 and then passed through a custom Python wrap/unwrap script that truncated the eight ECDSA private values; the keys of eight RSA-4096 issuers (G2B and G2C) stayed intact but were handled in that script's process memory, so eMudhra cannot show compliance with its certification practice statement, and it revoked them on 2026-11-07 with the reason cessationOfOperation after having said on 2026-10-19 that they were not impacted; its G2C issuers had issued end-entity certificates, the last on 2026-11-03, and no source says any RSA key leaked (eMudhra, Mozilla bug 2083449, 2026-11-10; eMudhra, Mozilla bug 2083449, 2026-10-19; BleepingComputer, 2026-11-11). The tracker says it is not known whether attackers used the flaw against other clients (Dennis Jackson, 2026-10-20).

Chrome blocked the intermediates on 2026-10-17, Firefox through OneCRL the same day, Microsoft platforms on 2026-10-20 and Apple products on 2026-10-22, and eMudhra revoked all eight (Dennis Jackson, 2026-10-20; BleepingComputer, 2026-10-20). Microsoft went further: an out-of-band Windows update of 2026-10-26 removes seven certificates, six eMudhra G3 roots and an AAA Certificate Services cross-sign, from the Windows trust list, and the same seven left the Edge trust list on 2026-10-27 (Microsoft, 2026-10-26). Google removed the root that signed them, emSign ECC Root CA - G3, from the Chrome Root Store, with the removal expected to reach devices on 2026-10-27 (Google, 2026-10-20). Go 1.27.3 and 1.26.10 filter chains that contain the intermediates in crypto/x509, tracked as CVE-2026-111943 (Go team, 2026-10-20), and GitLab's release of 2026-10-29 removes trust for the eight intermediates in self-managed CE and EE, with Runner 19.5.1 and the AI Gateway updated separately (GitLab, 2026-10-29).

Oracle's Security Alert of 2026-10-21 for CVE-2026-91403 (CVSS 3.1 9.1, JSSE) provided Java updates that distrust the impacted eMudhra intermediate CA certificates (Oracle, 2026-10-21), and a second Security Alert of 2026-10-24, CVE-2026-114820, removes the impacted root CA certificates and also covers the Java component of Oracle Database Server, Autonomous Health Framework and OPatch (Oracle, 2026-10-30). OpenJDK's guidance tells users of a standalone runtime to act immediately even if they updated in the past few days (OpenJDK, 2026-10-24).

Triage: a site that still chains to emSign ECC Root CA - G3 failing in Chrome after 2026-10-27, or a certificate that chains to one of the seven certificates Microsoft removed failing in Windows or Edge once the change reaches the device, is the announced root removal, not an attack (Google, 2026-10-20; Microsoft, 2026-10-26).

enabling anyone to forge trusted HTTPS certificates to impersonate any website against clients that have not yet removed trust in those CAs.

Google (Chrome Root Program and Android Security) 2026-10-20

many other clients do not consume revocation information and require software updates to ensure they no longer trust the compromised intermediates.

We do not know if attackers exploited the flawed key generation to target these clients.

Dennis Jackson (eMudhra intermediate CA compromise incident tracker) 2026-10-20

crypto/x509: mitigation for security concerns with a specific Certificate Authority

Go team (golang-announce) 2026-10-20

This Security Alert addresses CVE-2026-91403 by providing Java updates which distrusts the set of impacted intermediate CA certificates related to eMudhra.

Oracle (Security Alert CVE-2026-91403) 2026-10-21

This Security Alert addresses CVE-2026-114820 by providing Java updates that remove the set of impacted root CA certificates related to eMudhra.

Oracle (Security Alert CVE-2026-114820) 2026-10-24

take one of the following actions immediately; even if you have updated your runtime in the past few days.

OpenJDK (Compromised Certificates and OpenJDK Java Runtimes) 2026-10-24

Python has added a denylist for known compromised certificates to the "ssl" module to ensure user safety even without certificate revocation configured.

Python Software Foundation (security-announce, CVE-2026-115557) 2026-10-24

Chrome has told eMudhra that standard ACME clients do not replace certificates outside their renewal window unless they support ACME Renewal Information (ARI) or someone steps in by hand.

The Hacker News 2026-10-22

On October 26, Microsoft released an out-of-band Windows update that removes seven certificates associated with the affected hierarchies: six eMudhra G3 roots and an AAA Certificate Services cross-sign, from the Windows trust list.

Microsoft Security Response Center

GitLab has removed trust for eight eMudhra intermediate CA certificates whose private keys have been compromised.

GitLab

The Cisco PSIRT is not aware of any malicious use of the issue that is described in this advisory.

Cisco PSIRT

appliances with Client DPI-SSL enabled continued to trust certificate chains issued by compromised eMudhra intermediate Certificate Authorities (CAs)

SonicWall

The RSA issuers went through a different path as per our assessment of the code and are therefore not impacted.

eMudhra (Mozilla CA Program bug 2083449, comment 11) 2026-10-19

Eight RSA G2B/G2C subordinate CA certificates revoked (reason: cessationOfOperation) and withdrawn from service; CRLs and OCSP updated; migration of affected G2C subscribers initiated.

eMudhra (Mozilla CA Program bug 2083449, full incident report) 2026-11-10
Updaterun 2026-10-23T0256Z-intelheadlinesummaryaffected_productscvessourcesevidenceactionsbodyentities

On 2026-10-21 Oracle issued Security Alert CVE-2026-91403 and the OpenJDK project an advisory for the same event, which reaches Java runtimes as well; Oracle says it also applies to sandboxed Java Web Start and applet clients (Oracle, 2026-10-21). Affected are Oracle Java SE 8u511, 8u511-perf, 11.0.33, 17.0.21, 21.0.13, 25.0.5 and 27.0.1, GraalVM for JDK 17.0.21 and 21.0.13 and GraalVM Enterprise Edition 21.3.20, and OpenJDK lists 27.0.1, 25.0.5, 21.0.13, 17.0.21, 11.0.32.1 and 8u504 and earlier (Oracle, 2026-10-21; OpenJDK, 2026-10-21). NCSC.ch's advisory of 2026-10-22 lists the exploitation status as unknown and the OpenJDK guidance as the temporary mitigation (NCSC.ch, 2026-10-22).

Updaterun 2026-10-25T0256Z-intelheadlinesummarycvesaffected_productsentitiessourcesevidenceactionsbody

Oracle's second Security Alert of 2026-10-24, CVE-2026-114820 (CVSS 3.1 9.1, component JSSE, remotely exploitable without authentication through the component's APIs), provides Java updates that remove the impacted root CA certificates related to eMudhra (Oracle, 2026-10-24). Its affected list names Oracle Java SE 8u511-b32, 11.0.33.0.2, 17.0.21.0.2, 21.0.13.0.2, 25.0.5.0.2 and 27.0.1.0.2, and the OpenJDK advisory of the same day lists 27.0.1.0.2, 25.0.5.0.2, 21.0.13.0.2, 17.0.21.0.2, 11.0.32.1 and 8u504 and earlier as affected (Oracle, 2026-10-24; OpenJDK, 2026-10-24). OpenJDK tells users of a standalone runtime to act immediately even if they updated in the past few days, by installing an update whose release note names JDK-8395690 and CVE-2026-114820 or, failing that, by deleting the cacerts aliases emsignrootcag1, emsignrootcag2, emsigneccrootcag3 and comodoaaaca or enabling revocation checking (OpenJDK, 2026-10-24). The same page now says Debian, Devuan and Ubuntu OpenJDK packages need the keystore recreated by hand, because updating ca-certificates and ca-certificates-java does not refresh it, which replaces the earlier statement that updating the operating system's certificates suffices there (OpenJDK, 2026-10-24).

The Python Software Foundation announced CVE-2026-115557 on 2026-10-24: the ssl module now carries a denylist of known compromised certificates that is rejected whatever the SSLContext policy, so it works without revocation checking (Python Software Foundation, 2026-10-24). ENISA's record scores it 9.4 (CVSS 4.0) and lists CPython before 3.16.0 as affected, and the announcement names no release that carries the denylist (ENISA EUVD, 2026-10-24). The Python releases that carry the ssl denylist are 3.15.2, 3.14.10, 3.13.18, 3.12.16 and 3.11.18 (Python Insider, 2026-10-26), and Christian Heimes stresses in the announcement thread that pip before 26.2.2 keeps trusting the compromised intermediates whatever the system trust store holds, because it always loads its own vendored certifi (Dennis Jackson, 2026-10-20; Python Discourse, 2026-10-20).

Cisco's informational advisory, version 1.1 of 2026-10-24, lists as impacted with remediation a TLS policy that blocks the known eMudhra issuers on Secure Firewall Management Center, Duo Access Gateway 3.2.0, Duo Network Gateway 3.4.1, Duo Agentic Authorization Connector 1.0.1, ThousandEyes Enterprise Agent (Application-hosting Agent 5.2.2, 2026-10-23), Meraki MV Smart Camera Firmware (2026-11-18), IOS XR 26.4.1 (2026-11-30) and Ultra Cloud Core Subscriber Microservices Infrastructure 2026.04.1 (November 2026), keeps further products under investigation, and says Cisco PSIRT is not aware of malicious use (Cisco PSIRT, 2026-10-24).

eMudhra's board decided on 2026-10-22 to leave the global SSL/TLS certificate business, and its G1 RSA roots keep serving customers during the transition (eMudhra, 2026-10-22). The Hacker News relays Chrome's count of about 30,800 unexpired certificates under the emSign ECC Root CA - G3, which Chrome stops trusting on 2026-10-27, as of 2026-10-21, 99.9 percent of them issued through InCommon, and relays Chrome's point that standard ACME clients do not replace a certificate outside its renewal window unless they support ACME Renewal Information or someone steps in by hand (The Hacker News, 2026-10-22).

Updaterun 2026-11-01T0256Z-intelheadlinesummaryentitiesaffected_productssourcesevidencesourcing_noteactionsbodycves

Microsoft released an out-of-band Windows update on 2026-10-26 that removes seven certificates associated with the affected hierarchies, six eMudhra G3 roots and an AAA Certificate Services cross-sign, from the Windows trust list, and removed the same seven from the Edge trust list on 2026-10-27; removing a root is a separate and broader decision than blocking the compromised intermediates, which Microsoft had done through its Disallowed Certificate Trust List on 2026-10-20 (Microsoft, 2026-10-26). Microsoft tells organizations to keep automatic trust-list updates flowing, to make sure disconnected Windows devices receive the updated trust lists, and to replace certificates that chain to one of the seven before the change reaches their devices, and it warns that software that does not check revocation or the disallowed list could still accept certificates tied to the compromised keys if trust is restored locally (Microsoft, 2026-10-26).

Cisco's advisory is at version 1.5 of 2026-10-30. It lists remediation for Secure Firewall ASA, FTD and FMC (guidance page), Secure Email Gateway and Secure Email and Web Manager (updated automatically to Trusted Root 2.8, with the updatenow command where updates are manual) and Packaged and Unified Contact Center Enterprise (CSCwx36769); it dates the fixes for ISE and ISE-PIC to ISE 3.5P5 in December 2026 and 3.3P13 and 3.4P8 in April 2027, and still lists IOS XE Software, MDS 9000 and Nexus switches among the impacted products under investigation; Cisco says it is not aware of malicious use (Cisco PSIRT, 2026-10-30). GitLab's patch release of 2026-10-29 removes trust for the eight intermediates in self-managed CE and EE and says GitLab Runner 19.5.1 and the AI Gateway must be updated separately because they verify certificates on their own (GitLab, 2026-10-29). Python's expedited releases of 2026-10-26, 3.15.2, 3.14.10, 3.13.18, 3.12.16 and 3.11.18, now carry the built-in denylist for the compromised intermediates (Python Insider, 2026-10-26). Oracle's revision 2 of Security Alert CVE-2026-114820, dated 2026-10-30, adds the Java component of Oracle Database Server (19.3 to 19.32, 21.3 to 21.23 and 23.4.0 to 23.26.3, not client-only installations), Autonomous Health Framework Trace File Analyzer 26.3 to 26.10, OPatch 12.2.0.1.16 to 12.2.0.1.52 and Hospitality Cruise Shipboard Property Management 23.3.4 to 23.3.6, each remotely exploitable without authentication at CVSS 3.1 9.1 (Oracle, 2026-10-30).

Correctionrun 2026-11-01T1312Z-auditbodyevidence

Python 3.15.1, 3.14.9 and 3.13.17 do not carry the protection: the releases whose ssl module blocks the compromised eMudhra keys are 3.15.2, 3.14.10, 3.13.18, 3.12.16 and 3.11.18 (Python Insider, 2026-10-26). A host on 3.15.1, 3.14.9 or 3.13.17 still needs the later release.

Updaterun 2026-11-08T0256Z-intelsummaryaffected_productssourcesactionssourcing_notebody

Cisco's advisory is at version 1.8 of 2026-11-06 (1.6 on 2026-11-04 and 1.7 on 2026-11-05). IOS XE Software, which version 1.5 still listed among the products under investigation, now has a CA-trust distrust guide and a GuestShell bug entry (CSCwx51613) (Cisco PSIRT, 2026-11-06). Several routing and switching products have no remediation yet: MDS 9000 releases 9.4(1) to 9.4(5a), Nexus 3000 and standalone NX-OS Nexus 9000 releases 9.3(9) to 9.3(18) and the 10.x trains except 10.1, and ACI-mode Nexus 9000 trains 15.x and 16.x are listed as impacted (Cisco PSIRT, 2026-11-06). Cisco still says it is not aware of malicious use (Cisco PSIRT, 2026-11-06).

Apple's support page of 2026-10-30 says that the curl, git, python3, ruby, perl and openssl that ship with macOS or the Xcode command-line tools check certificates against /etc/ssl/cert.pem and apply neither Apple's block nor revocation, so they keep trusting the intermediates until a future macOS update, which Apple has not dated; apps and tools that keep their own root list need the developer's update (Apple, 2026-10-30). Administrators can remove emSign ECC Root CA - G3 from the file and, as an optional step, AAA Certificate Services to stop the six Sectigo cross-signed certificates as well, which Apple warns can leave tools that read only that file unable to verify some websites whose chains run through unaffected intermediates; a macOS software update can replace the file with Apple's version, so the check has to be repeated after each update until the one that carries Apple's change (Apple, 2026-10-30). heise reports that macOS 27.2, which brought no fix, undid the workaround for users who had applied it, that the macOS 27.3 developer beta replaces the file, and that the final release will take at least until December (heise, 2026-11-06).

Google's post now carries an update of 2026-11-04: Chrome 153 and higher will no longer trust by default TLS server certificates that validate to emSign Root CA - G1 when their earliest Signed Certificate Timestamp is dated after 2026-11-16 23:59:59 UTC, and certificates whose earliest SCT is on or before that time are unaffected (Google, 2026-11-04). Apple's page dates its block of the twelve intermediate certificates to 2026-10-19, three days before the 2026-10-22 the incident tracker and BleepingComputer gave for Apple devices, and its block of the emSign ECC Root CA - G3 root to 2026-10-23 (Apple, 2026-10-30).

Updaterun 2026-11-11T0256Z-intelsummaryentitiesaffected_productssourcesevidenceactionsbodyheadlinesourcing_note

SonicWall's informational advisory SNWLID-2026-0021 of 2026-11-10, which has no CVE and no workaround, says SonicOS appliances with Client DPI-SSL enabled continued to trust certificate chains issued by the compromised eMudhra intermediate CAs because the firewall's local certificate store trusted the underlying roots, and that the firewall then re-signed traffic from the impacted servers with its local DPI-SSL CA certificate, preventing client browsers from rejecting connections signed by the untrusted intermediates (SonicWall, 2026-11-10; SonicWall advisory data, 2026-11-10). SonicWall removed the affected root certificates from the SonicOS certificate store and added blocking logic for the compromised chain. Affected are Gen7 hardware firewalls (TZ 270 to TZ 670, NSa 2700 to 6700, NSsp 10700 to 15700) and Gen7 NSv up to 7.3.4-7013, fixed in 7.3.4-7015 and higher, and Gen8 hardware (TZ 80 to TZ 680, NSa 2800 to 5800) and Gen8 NSv up to 8.2.2-8015, fixed in 8.2.3-8015 and higher; a Gen7 firewall that took only 7.3.4-7013 is therefore still affected (SonicWall, 2026-11-10).

Apple revised its support page on 2026-11-10: from macOS 27.2.1 the command-line tools no longer accept the twelve intermediate certificates, and the two roots they chain to, with three more eMudhra roots, leave /etc/ssl/cert.pem; macOS 26.7.3 and 15.8.3 carry the same protection, and after updating the manual removal need not be repeated (Apple, 2026-11-10). The revised page no longer carries the block dates of its 2026-10-30 version, so the 2026-10-22 date of the tracker and BleepingComputer stands for Apple's block.

Microsoft's post carries an update of 2026-11-10: the remaining eMudhra roots leave Microsoft products starting 2026-11-16, the ten remaining roots leave the Windows trusted root list through the automatic certificate-trust update, Edge and WebView2 drop default trust for emSign Root CA - G1, C1, ECC Root CA and Root TLS CA - G1 on the same date, Azure Linux images follow that day, and the .NET container images and the Microsoft Build of OpenJDK follow upstream releases (Microsoft, 2026-11-10). Cisco's advisory is at version 1.9 of 2026-11-10, which updates the products under investigation, impacted and not impacted (Cisco PSIRT, 2026-11-10).

Updaterun 2026-11-12T0255Z-inteltitleheadlinesummarysourcesevidencesourcing_noteactionsbody

eMudhra posted its full incident report in the Mozilla bug on 2026-11-10 (eMudhra, Mozilla bug 2083449, 2026-11-10). For the eight RSA-4096 issuers (G2B and G2C) it says the key integrity is intact, all signatures verifying, but that during re-import the private-key material was handled in the volatile memory of a Python process on the ceremony host, which is not consistent with its certification practice statement, so the RSA issuers are treated as not meeting it; it adds that logs cannot reliably establish or exclude how that material was handled (eMudhra, Mozilla bug 2083449, 2026-11-10). It identified this in early November after a root-program discussion, revoked the eight issuers on 2026-11-07 with the reason cessationOfOperation, not the compromise reason used for the ECDSA set, and had written on 2026-10-19 that the RSA issuers were not impacted (eMudhra, Mozilla bug 2083449, 2026-11-10; eMudhra, Mozilla bug 2083449, 2026-10-19). The G2C issuers were put into production in May 2026 and issued end-entity certificates, the last on 2026-11-03, after which issuance from them stopped; BleepingComputer reports that eMudhra says the affected customer certificates were replaced or migrated, and that the company has not detected malicious use of the keys (eMudhra, Mozilla bug 2083449, 2026-11-10; BleepingComputer, 2026-11-11). eMudhra also decided to exit public TLS, with all issuance from its emSign Root CA - G1 hierarchy to stop before 2026-11-16 and an independent review due 2026-12-04 (eMudhra, Mozilla bug 2083449, 2026-11-10). No page read from Google, Microsoft, Apple, Mozilla or the incident tracker names the G2B or G2C issuers or says a vendor blocked them.

Improvementrun 2026-11-15T1407Z-audittitlesummarysourcessourcing_noteactionsbody

Microsoft's post now carries an update dated 2026-11-12 with a per-product table: Visual Studio Code 1.147.0 is due with fixes on 2026-11-18 after the node-vsce-sign package of 2026-11-12, Azure CLI 2.93.0 is due on 2026-11-16 to remove two more eMudhra roots, emSign Root CA - C1 and emSign ECC Root CA - C3, from its bundled trust store after 2.92.0 blocked the G3 root on 2026-11-03, the .NET SDK follows in December 2026, and the API Management self-hosted gateway and the Microsoft Build of OpenJDK follow the Mozilla release of 2026-11-16 (Microsoft, 2026-11-12).

incident21 Oct 03:43Zmulti-sourceOpen finding →
Sources: Google (Chrome Root Program and Android Security) · Dennis Jackson (eMudhra intermediate CA compromise incident tracker) · Mozilla Security Blog · Go team (golang-announce) · BleepingComputer · Oracle (Security Alert CVE-2026-91403) · OpenJDK (Vulnerability Advisory 2026/10/21) · NCSC.ch Security Hub (advisory 13091) · Oracle (Security Alert CVE-2026-114820) · OpenJDK (Vulnerability Advisory 2026/10/24) · OpenJDK (Compromised Certificates and OpenJDK Java Runtimes) · Python Software Foundation (security-announce, CVE-2026-115557) · ENISA EUVD (EUVD-2026-109299) · Cisco PSIRT (cisco-sa-emudhra-info, version 1.1) · Python Discourse (eMudhra information for Python users) · The Hacker News · eMudhra (press release) · Microsoft Security Response Center (updated 2026-10-27) · Cisco PSIRT (cisco-sa-emudhra-info, version 1.5) · GitLab (patch release 19.5.3) · Python Insider (release post) · Dennis Jackson (eMudhra intermediate CA compromise incident tracker, update of 28 October) · Oracle (Security Alert CVE-2026-114820, revision 2) · Cisco PSIRT (cisco-sa-emudhra-info, version 1.8) · Google (Chrome Root Program and Android Security, update of 2026-11-04) · Apple Support (information on the compromised eMudhra intermediate CAs, translated from German) · heise online (translated from German) · SonicWall (informational advisory SNWLID-2026-0021) · SonicWall PSIRT (advisory data for SNWLID-2026-0021) · Apple Support (information on the compromised eMudhra intermediate CAs, revised 2026-11-10, translated from German) · Microsoft Security Response Center (updated 2026-11-10) · Microsoft Security Response Center (updated 2026-11-12) · Cisco PSIRT (cisco-sa-emudhra-info, version 1.11) · eMudhra (Mozilla CA Program bug 2083449, full incident report) · eMudhra (Mozilla CA Program bug 2083449, comment 11)

Co-occurring entities

Derived: referenced by the same focused operational entries (weekly summaries and report roundups don't count); ×N counts the shared entries.

Where this entity is cited

  • Threats1

Source distribution

  • openjdk.org3 (11%)
  • bleepingcomputer.com2 (7%)
  • bugzilla.mozilla.org2 (7%)
  • oracle.com2 (7%)
  • blog.google1 (4%)
  • blog.mozilla.org1 (4%)
  • blog.python.org1 (4%)
  • discuss.python.org1 (4%)
  • other14 (52%)
All cited sources (27)