Home / Security / Advisories / NTAP-20260617-0014
NTAP-20260617-0014 — CVE-2026-42769 OpenSSL Vulnerability in NetApp Products
Published 2026-06-17 · Updated 2026-10-07 · Status: Interim · Exploitation: Public · Severity: MEDIUM 5.3 · ONTAP affected: Yes
Product family: Active IQ Unified Manager · SolidFire / NetApp HCI · NetApp Console / BlueXP · ONTAP · Brocade SAN firmware · Other NetApp products | ONTAP-relevant | highest CVSS: 5.3
CVEs in this advisory
- CVE-2026-42769 — MEDIUM · CVSS 5.3 · site index
What the CVE records say
CVE-2026-42769 — Issue Summary: An error in the callback used to verify the certificate provided in a Root CA key update Certificate Management Protocol (CMP) message response rendered the certificate validation ineffectual, which could lead to escalation of credentials from the Registration Authority (RA) level to the root Certification Authority (root CA) level. Impact Summary: The Registration Autority could replace the root CA certificate for the CMP clients with an arbitrary root CA certificate. One of the parts of the Certificate Management Protocol (CMP), specified in RFC 9810, is Root Certification Authority (root CA) key Rollover, which is sent by the server in a message with type 'id-it-rootCaKeyUpdate'. As part of these messages, 'newWithOld' certificate, the new root CA certificate signed with the old root CA key, is provided, and verifying its signature is crucial for transferring the trust from the old CA key to the new one. The 'id-it-rootCaKeyUpdate' messages are expected to be processed with OSSL_CMP_get1_rootCaKeyUpdate(), that is expected to verify the 'newWithOld' certificate. A typo in the certificate chain building code led to adding an incorrect certificate ('newWithOld' instead of 'oldRoot') to the certificate chain, rendering the certificate verification process ineffectual (only the issuer name and the algorithm OIDs were verified by other parts of the verification code). An attacker who already has credentials that satisfy the CMP message protection checks can generate a new key pair and use a crafted self-signed certificate in its 'id-it-rootCaKeyUpdate' CMP messages which affected CMP clients would accept as a new trust anchor. Significant preconditions for the attack (having valid RA-level credentials) are the reason the issue was assigned Low severity. The FIPS modules are not affected by this issue, as the affected code is outside the OpenSSL FIPS module boundary.
Impact
Successful exploitation of this vulnerability could lead to disclosure of sensitive information.
Affected products
- Active IQ Unified Manager for VMware vSphere
- Management Services for Element Software and NetApp HCI
- NetApp Console Agent Container (adc)
- NetApp Console Agent Container (cbs)
- NetApp Console Agent Container (cbs-backend)
- NetApp HCI Baseboard Management Controller (BMC) - H610S
- ONTAP Select Deploy administration utility
- Brocade Fabric Operating System Firmware
- Brocade SAN Navigator (SANnav)
- Cloud Volumes ONTAP Mediator
- Global File Cache
- NetApp Console Agent Container (alert-service-client)
References
- https://openssl-library.org/news/secadv/20260609.txt ↗
- https://openssl-library.org/news/vulnerabilities/index.html#CVE-2026-42769 ↗
What to do
- Check the affected products listed above against the official advisory's affected-versions table — that is where the exact ONTAP 9 release, ONTAP tool, or management product versions are named.
- If affected and a fixed release exists, plan the upgrade — see the ONTAP upgrade runbook.
- If exploitation is listed as "active", treat remediation as urgent and review exposure (management LIFs, ONTAP S3, SnapMirror endpoints).
- Harden in parallel: security hardening baseline and ransomware protection on ONTAP.
Related reading
- Common ONTAP problems (FAQ) — plain-language symptoms and fixes
- ONTAP security hardening — baseline lockdown guidance
- Ransomware protection on ONTAP — SnapLock, SnapMirror vaulting, Anomaly Detection
- ONTAP error messages index — EMS/WAFL/NFS/SnapMirror messages
- Every NetApp advisory published in 2026