From the NetApp edition of November 9, 2026
NetApp advisory NTAP-20261027-0001 v9.0: eMudhra CA compromise leaves ONTAP 9, StorageGRID and Trident Affected with workarounds; AIDE still Investigating
NetApp Product Security · Storage infrastructure (cross-sector) · Global
- Publisher
- NetApp Product Security
- Original publication
- Initial release 2026-10-27; v9.0 last updated 2026-11-09
- Source retrieved
- 2026-11-10
- Event date
- 2026-10-18
What happened
NetApp's advisory for CVE-2026-22063 (CVSS 4.0 6.0 Medium, status Interim) states eight eMudhra intermediate CA private keys were compromised and revoked on 18 October 2026, enabling man-in-the-middle attacks. v9.0 (9 Nov) adds fixes for E-Series SANtricity OS (11.90R1, 12.10R1) and the e-series Console Agent container. ONTAP 9 is Affected: the 'AAA Certificate Services' root was preinstalled before 9.18.1, and the workaround is deleting it with 'security certificate delete' at advanced privilege. StorageGRID (KB CSG-28116), Trident, Trident Autosupport, Data Infrastructure Insights agents and others are also Affected. AI Data Engine (AIDE) remains under Investigating; AIDE MCP Server and Langchain Retriever are Not Affected. Why now: first coverage; the 9 Nov revision adds fixes, and ONTAP 9 remains unfixed.
Why it matters
SLED NetApp estates commonly run ONTAP releases older than 9.18.1, so the preinstalled trust anchor is likely present on many arrays serving agency, campus and district data, including those feeding AI pipelines. Trident is also Affected, which matters for Kubernetes-based research and AI platforms.
Evidence and measured results
Official vendor advisory. Summary, impact, CVSS and version/date confirmed on the headless-rendered page; affected, investigating and fix lists from the official adv_api JSON. NetApp cites eMudhra's statement and a CERT-In note; those references were not opened. No independent evidence of exploitation against NetApp products was found.
Limitations and uncertainty
Vendor-claim advisory, Interim status. Severity is Medium and exploitation requires high attack complexity and user interaction per the CVSS vector. AIDE status unresolved. Prevalence of pre-9.18.1 ONTAP in SLED is interpretation, not measured.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-11-10; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Customers may unknowingly trust a compromised certificate chain on storage and container platforms that serve sensitive and AI data.
- Stakeholders
- Storage administrators
- Security/PKI team
- Kubernetes platform team
- Change advisory board
- Discovery questions
- Which ONTAP versions below 9.18.1 are in service?
- Do any integrations rely on certificates chained to eMudhra?
- Is Trident used for research or AI Kubernetes clusters?
- Is AIDE in evaluation or production?
- Value hypothesis
- A short trust-store review can remove an unnecessary trust anchor with limited disruption, reducing MITM exposure.
- Potential engagement
- A bounded certificate inventory and remediation-support engagement across ONTAP, StorageGRID and Trident.
- Unsupported claims
- That AIDE is unaffected (still Investigating)
- Any known exploitation against NetApp customers
- That an ONTAP upgrade is required (workaround is certificate deletion)
- High severity (rated Medium 6.0)
Pre-sales engineering
Role takeaway
- Fit
- Relevant to customers on ONTAP before 9.18.1, StorageGRID, Trident or listed monitoring agents.
- Architecture and integration
- ONTAP trust store managed via 'security certificate' commands at advanced privilege; StorageGRID via KB guidance; Trident within Kubernetes trust configuration.
- Prerequisites
- ONTAP version and certificate inventory
- Admin access at advanced privilege
- List of TLS-dependent integrations
- Non-production test environment
- Constraints
- No ONTAP fix listed; workaround only
- AIDE status unresolved
- Removing roots may break legacy integrations
- Security
- Removes a compromised trust path enabling MITM; CVSS 4.0 vector indicates high attack complexity and user interaction required.
- Proof of value
- Confirm the root is absent after deletion
- Verify all dependent TLS integrations reconnect
- Confirm no eMudhra-chained customer certificates remain
Delivery
Role takeaway
- Work
- Inventory and remove the affected root/certificates under change control, validate integrations, document exceptions and re-check the advisory.
- Dependencies
- Change approval
- PKI/security team input
- Kubernetes platform owners for Trident
- Ownership
- Storage operations owns ONTAP/StorageGRID changes; platform team owns Trident; security accepts exceptions.
- Skills and adoption
- Requires PKI and ONTAP advanced-privilege command familiarity; brief runbook recommended.
- Governance checkpoints
- Pre-change integration dependency review
- Change approval
- Post-change verification sign-off
- AIDE status re-check before production use
- Acceptance criteria
- Affected root removed on 100% of in-scope ONTAP systems or exception recorded
- Zero integration outages attributable to the change
- Trident trust configuration reviewed in every in-scope cluster
- Risks
- Breaking an integration that depended on the root
- Advisory scope changes
- Overlooked customer-installed certificates
Implementation considerations
Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.
Architecture and integration
What must connect, and where does the AI sit in the workflow?
Trust-store hygiene is a configuration task on ONTAP (certificate deletion) rather than a software upgrade for releases before 9.18.1; Kubernetes (Trident) and monitoring agents need separate review.
Governance
Who approves, reviews and stays accountable for outcomes?
Certificate-trust changes should go through change control because removing a root can break integrations that relied on it; record which systems retain it and why.
Security and privacy
What data, permissions and controls need testing?
MITM risk on TLS connections that trust the compromised chain; affects confidentiality (CVSS VC:H) of management and data-service connections that validate against it.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Small operational task; requires PKI awareness among storage staff.
Procurement
What should contracts, pricing and exit terms secure?
None directly; AIDE evaluations should note open advisory status.
Operating model
Which teams own the service once it runs?
Trust-store review should become routine after CA distrust events.
Publication history
- 2026-11-09NetApp · Issue 113 resources
Stable resource ID: netapp-advisory-ntap-20261027-0001-emudhra-ca-compromise-v9-20261109