Cisco Investigates Products After eMudhra Root CAs Distrusted Over Private Key Exposure
Key Facts
- Cisco's advisory cisco-sa-emudhra-info-ScS22A1r was first published on October 23, 2026, and last updated on November 16, 2026 (version 1.12, interim).
- Eight eMudhra intermediate CAs are affected: six TLS issuing CAs and two code-signing CAs, all cross-signed by Sectigo's AAA Certificate Services root.
- eMudhra says a flaw in its April 30, 2025 key generation ceremony produced a second set of weak keys that were published to browser root stores.
- Cisco says any product that trusts the compromised intermediates is affected, whether through Trusted Root Store bundles, embedded certificates or third-party trust mechanisms.
- Cisco PSIRT is aware of the public announcement but is not aware of malicious use of the issue.
Cisco has published an interim informational advisory to track which of its products trust eight eMudhra intermediate certificate authorities whose private keys were found to be weak, allowing anyone holding them to forge trusted TLS and code-signing certificates. The advisory, cisco-sa-emudhra-info-ScS22A1r, was first published on October 23, 2026, and last updated on November 16 at 22:25 GMT. Cisco says no workarounds are available and that the investigation is continuing.
eMudhra disclosed the underlying problem on October 21. According to the company, a flaw in the key generation ceremony held on April 30, 2025, caused a wrap/unwrap step to produce a second set of weak keys alongside the intended strong keys. The weak keys were the ones published to browser root stores. eMudhra says its infrastructure was not compromised, and no data was breached.
What Broke in the Key Ceremony
The eight affected issuing CAs comprise six TLS CAs covering domain-validated, organization-validated and extended-validation certificates, plus two code-signing CAs. All eight were cross-signed by Sectigo’s AAA Certificate Services root in May 2025. That cross-signature meant the weak keys were trusted by almost every device, browser and operating system, even where the eMudhra roots were not natively trusted.
The practical risk is certificate forgery. Anyone in possession of a weak private key can issue a fraudulent TLS certificate for any domain, or sign malicious software so that it appears to come from a trusted publisher. Cisco’s advisory says a researcher demonstrated that the keys could be brute-forced within seconds because of the entropy failure.
Cisco’s exposure is a trust-store problem rather than a vulnerability in one product. Any Cisco product that trusts the compromised intermediate certificates is affected, whether that trust is managed through Cisco’s Trusted Root Store bundles, embedded certificates, or third-party trust mechanisms.
Which Cisco Products Are Affected
Cisco lists a set of products still under investigation, including Catalyst Center, Evolved Programmable Network Manager, Secure Malware Analytics in cloud and private-cloud deployments, Cloud Network Controller, vEdge routers, and Meraki devices and vMX.
Products with remediation steps include IOS and IOS XE software and GuestShell, Secure Firewall ASA, Firepower Management Center, Secure Firewall Threat Defense, Packaged Contact Center Enterprise, Unified Contact Center Enterprise, Real Time Monitoring Tool, and Unified Customer Voice Portal. Cisco has published a separate IOS XE and GuestShell guide for auditing and removing trust in the affected hierarchies.
Impacted products with software fixes span a long list, including Adaptive Security Device Manager, Application Policy Infrastructure Controller, ASR 5000 StarOS, RoomOS collaboration endpoints, Crosswork Data Gateway, Cyber Vision, Duo, Identity Services Engine, Intersight Virtual Appliance, IOS XR, IP phones, Nexus and MDS switches, Network Services Orchestrator, and several Ultra Cloud Core and Ultra Packet Core components.
Remediation: Remove Trust and Apply Fixes
Several products update their trust stores without customer action. Secure Email and Web Manager and Secure Email Gateway move to Trusted Root 2.8 through the updater, or through cli->updatenow where updates are configured manually. Unified Customer Voice Portal refreshes its untrusted certificate list in the background. Duo, Secure Access, Meraki Dashboard and Webex Meetings are described as cloud-remediated.
For products that require an upgrade, Cisco lists target releases that include:
- ASDM and Security Manager: 11.0.32.1, March 2027
- APIC: 6.3.1, December 2026
- IOS XR: 26.4.1, due 30 November 2026
- ISE and ISE-PIC: 3.5P5 in December 2026; 3.3P13 and 3.4P8 in April 2027
- NSO (container only): 6.8 due 19 November 2026; 6.6.10 and 6.7.5 due 17 November 2026
- RoomOS on-premises: 11.41.2.3 and 26.7.4.3
Cisco says the issue is not limited to a single validation path. The IOS XE guide notes that each affected key appears in both an original emSign-issued CA certificate and a Sectigo cross-signed certificate, producing 16 certificates in total: 12 for TLS and four for code signing. Both forms must be included in an audit because they have the same subject and public key but different issuers, serial numbers and fingerprints.
What Administrators Should Do Now
Start by inventorying trust stores for both the original and cross-signed forms of the eight issuing CAs. Removing only a cached intermediate is not enough, because a peer can still present a copy through a remaining trusted path.
Remove directly trusted affected sub-CAs from trustpoints and downloaded trustpool bundles. Cisco’s guidance is explicit that revocation settings should not be relied on to override direct trust in a compromised CA.
Root removal is an optional extra step. Deleting the AAA Certificate Services root can interrupt unrelated legitimate certificate chains, so assess dependencies first. Where a required root stays trusted, the guide says revocation checking must reject the affected original, cross-signed and longer chains, and validation must fail if neither CRL nor OCSP provides usable status.
Cisco PSIRT says it is aware of the public announcement but not aware of any malicious use of the issue. The advisory remains interim, and Cisco says it will update the affected-product lists as its investigation progresses. Organizations that cannot immediately remove trust should track the advisory and apply the fixed release for each product line as it becomes available.
Sources & References
- Cisco informational advisory: emergency distrust of eMudhra root and intermediate certificate authorities. https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-emudhra-info-ScS22A1r
- Cisco IOS XE and GuestShell CA trust guidance for the eMudhra distrust. https://www.cisco.com/c/en/us/support/docs/ios-nx-os-software/ios-xe-17/226548-cisco-ios-xe-and-guestshell-ca-trust.html
- eMudhra statement on the distrust of select global TLS intermediate and root CAs. https://emudhra.com/en/press-release/emudhra-statement-distrust-global-tls-intermediate-root-ca
SecurityXP delivers cybersecurity news, vulnerability analysis, data breach reports, and threat intelligence.
Security Digest
The most important cybersecurity stories, CVE alerts, and threat intelligence — one concise email. Unsubscribe anytime.
Related Articles
Cisco Unified CM Flaw CVE-2026-20230 Actively Exploited in the Wild
Cisco Unified Communications Manager has a serious vulnerability, tracked as CVE-2026-20230 (CVSS score of 8.6), that attackers are already exploiting. The...
Kenna: RISK-BASED VULNERABILITY MANAGEMENT
Why You Should Consider More Than CVSS As previously mentioned, one typical method of sorting and prioritising which vulnerabilities to fix first is patching vulnerabilities that have a CVSS score in
Best Cloud SaaS Governance Practices from CSA
Introduction Infrastructure as Service security is almost always the focus when discussing cloud security. platforms as a service (PaaS) and infrastructure as a service (IaaS). In spite of the fact...
Cisco SD-WAN Manager Under Attack, No Patch Yet
Cisco has confirmed active exploitation of a high-severity vulnerability in Catalyst SD-WAN Manager. The flaw, CVE-2026-20245, scores 7.8 on the CVSS scale.