Home / Security / Advisories / NTAP-20260204-0015
NTAP-20260204-0015 — CVE-2025-66199 OpenSSL Vulnerability in NetApp Products
Published 2026-02-04 · Updated 2026-10-07 · Status: Interim · Exploitation: Public · Severity: MEDIUM 5.9 · ONTAP affected: Yes
Product family: Brocade SAN firmware · SolidFire / NetApp HCI · NetApp Console / BlueXP · Other NetApp products · ONTAP · SnapCenter | ONTAP-relevant | highest CVSS: 5.9
CVEs in this advisory
- CVE-2025-66199 — MEDIUM · CVSS 5.9 · site index
What the CVE records say
CVE-2025-66199 — Issue summary: A TLS 1.3 connection using certificate compression can be forced to allocate a large buffer before decompression without checking against the configured certificate size limit. Impact summary: An attacker can cause per-connection memory allocations of up to approximately 22 MiB and extra CPU work, potentially leading to service degradation or resource exhaustion (Denial of Service). In affected configurations, the peer-supplied uncompressed certificate length from a CompressedCertificate message is used to grow a heap buffer prior to decompression. This length is not bounded by the max_cert_list setting, which otherwise constrains certificate message sizes. An attacker can exploit this to cause large per-connection allocations followed by handshake failure. No memory corruption or information disclosure occurs. This issue only affects builds where TLS 1.3 certificate compression is compiled in (i.e., not OPENSSL_NO_COMP_ALG) and at least one compression algorithm (brotli, zlib, or zstd) is available, and where the compression extension is negotiated. Both clients receiving a server CompressedCertificate and servers in mutual TLS scenarios receiving a client CompressedCertificate are affected. Servers that do not request client certificates are not vulnerable to client-initiated attacks. Users can mitigate this issue by setting SSL_OP_NO_RX_CERTIFICATE_COMPRESSION to disable receiving compressed certificates. The FIPS modules in 3.6, 3.5, 3.4 and 3.3 are not affected by this issue, as the TLS implementation is outside the OpenSSL FIPS module boundary. OpenSSL 3.6, 3.5, 3.4 and 3.3 are vulnerable to this issue. OpenSSL 3.0, 1.1.1 and 1.0.2 are not affected by this issue.
Impact
Successful exploitation of this vulnerability could lead to Denial of Service (DoS). <br><br> NetApp Manageability SDK:<br> OpenSSL was removed in 9.8P8. <br> ONTAP Select Deploy administration utility:<br> Affected only in version 9.18.1
Affected products
- Brocade SAN Navigator (SANnav)
- Management Services for Element Software and NetApp HCI
- NetApp Console Agent Container (cbs-backend)
- NetApp HCI Baseboard Management Controller (BMC) - H610S
- NetApp LOADER 8.x
- ONTAP Select Deploy administration utility
- Cloud Volumes ONTAP Mediator
- Global File Cache
- NetApp Console Agent Container (alert-service-client)
- NetApp Console Agent Container (alertmanager)
- NetApp Console Agent Container (cadvisor)
- NetApp Console Agent Container (certificates)
References
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