
Security advisory • Cisco product response to the eMudhra CA-key compromise[1]
Cisco maps product impact and fixes for eMudhra certificate compromise[1]
Cisco’s interim version 1.1 advisory identifies impacted products, cloud-remediation states, software targets and products still under investigation after the eMudhra intermediate-certificate private-key compromise.[1]
Reporting cutoff: 2026-10-24T21:46:41-04:00 (EDT; America/New_York) / 2026-10-25T01:46:41Z (UTC).
Exposure predicate: treat a deployment as a candidate for action only when the exact product or component appears in Cisco’s impacted list and the deployment trusts an affected eMudhra intermediate through a Cisco trust bundle, an embedded certificate or another trust mechanism. A product listed only as “under investigation” is not yet confirmed vulnerable.[1]
Advisory state
Cisco last updated the notice at 20:55 GMT on October 24, 2026. It remains version 1.1, Interim, and says no general workarounds are available; product-specific actions appear in the vulnerable-products section.[1]
Product disposition at the cutoff
| Disposition | Product | Cisco’s stated action or target |
|---|---|---|
| Remediation steps | Secure Firepower Management Center (FMC) Software | Use Cisco’s linked FMC TLS-policy guidance; Cisco warns that this control does not cover every scenario or replace trust-store remediation and certificate replacement.[1][2] |
| Software target | Application-hosting Agent 5.2.2 for ThousandEyes Enterprise Agent | October 23, 2026.[1] |
| Upgrade | Duo Access Gateway | Upgrade to 3.2.0 using Cisco’s linked release instructions.[1] |
| Upgrade | Duo Agentic Authorization Connector | Upgrade to 1.0.1 using Cisco’s linked instructions.[1] |
| Upgrade | Duo Network Gateway | Upgrade to 3.4.1 using Cisco’s linked release instructions.[1] |
| Future target | IOS XR Software | 26.4.1, targeted for November 30, 2026.[1] |
| Future target | Meraki MV Smart Camera Firmware | Targeted for November 18, 2026.[1] |
| Future target | Ultra Cloud Core — Subscriber Microservices Infrastructure | 2026.04.1, targeted for November 2026.[1] |
Cloud services
| Service | State |
|---|---|
| Duo | Duo cloud is remediated; no customer action required.[1] |
| Secure Access (Cloud) | Secure Access cloud is remediated; no customer action required.[1] |
| Meraki Dashboard | Cloud remediation in progress; no customer action required. “In progress” is not complete.[1] |
Still under investigation
Cisco’s impacted-but-still-under-investigation list includes Identity Services Engine, ISE Passive Identity Connector, Policy Suite, Secure Firewall Adaptive Security Appliance, Secure Firewall Threat Defense, Secure Network Analytics and Secure Web Appliance.[1]
Confirmed not vulnerable
Cisco also publishes a product-specific confirmed-not-vulnerable list. That status should be applied only to the exact named product or component, not generalized across similarly named products.[1]
ThousandEyes naming caution: the captured advisory places “ThousandEyes Enterprise Agent” in both the still-under-investigation and confirmed-not-vulnerable sections, while separately listing “Application-hosting Agent 5.2.2 (ThousandEyes Enterprise Agent)” as impacted. Cisco does not reconcile those labels in the advisory; verify the exact component and deployment before acting.[1]
Practical steps
- Inventory precisely. Match exact product, component and installed release; then determine whether that deployment trusts an affected intermediate through the mechanism Cisco describes.[1]
- Keep investigation states separate. Do not treat a product that Cisco lists only as under investigation as confirmed vulnerable.[1]
- Respect cloud-service state. Do not create customer work for Duo or Secure Access cloud, and keep tracking Meraki Dashboard until Cisco changes “in progress” to a completed state.[1]
- Plan upgrades under change control. Treat future targets as dates, not released fixes; consult the relevant Cisco advisory for a complete upgrade path and verify hardware and configuration support before deployment.[1]
- Use the FMC control as limited containment. Follow Cisco’s exact TLS-policy procedure, continue trust-store remediation and certificate replacement, and do not import a compromised CA into Trusted CAs.[2]
- Recheck before any change. Cisco says the interim advisory will be updated as more information becomes available.[1]
What remains unknown
Final dispositions remain unknown for products still under investigation. Future target dates may change, and the advisory does not resolve the ThousandEyes naming overlap. Cisco PSIRT says it is not aware of malicious use, which is not proof that none occurred.[1]
