Home / Security / Advisories / NTAP-20260227-0008

NTAP-20260227-0008 — CVE-2022-40735 Diffie-Hellman Key Exchange Protocol Vulnerability in NetApp Products

Published 2026-02-27 · Updated 2026-08-06 · Status: Interim · Exploitation: Public · Severity: HIGH 7.5 · ONTAP affected: Yes

Official advisory: NTAP-20260227-0008 on security.netapp.com ↗. Affected versions, fixed releases, and workarounds live there — this page is a summary.

Product family: Astra Control · E-Series / SANtricity · Baseboard management controllers · Other NetApp products · ONTAP · SolidFire / NetApp HCI · NetApp Console / BlueXP  |  ONTAP-relevant  |  highest CVSS: 7.5

CVEs in this advisory

What the CVE records say

CVE-2022-40735 — The Diffie-Hellman Key Agreement Protocol allows use of long exponents that arguably make certain calculations unnecessarily expensive, because the 1996 van Oorschot and Wiener paper found that "(appropriately) short exponents" can be used when there are adequate subgroup constraints, and these short exponents can lead to less expensive calculations than for long exponents. This issue is different from CVE-2002-20001 because it is based on an observation about exponent size, rather than an observation about numbers that are not public keys. The specific situations in which calculation expense would constitute a server-side vulnerability depend on the protocol (e.g., TLS, SSH, or IKE) and the DHE implementation details. In general, there might be an availability concern because of server-side resource consumption from DHE modular-exponentiation calculations. Finally, it is possible for an attacker to exploit this vulnerability and CVE-2002-20001 together.

Impact

Successful exploitation of this vulnerability could lead to Denial of Service (DoS). <br><br> E-Series SANtricity OS Controller Software:<br> Affected only when SSH is enabled - it is disabled by default.

Affected products

Official fixes

References

What to do

  1. 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.
  2. If affected and a fixed release exists, plan the upgrade — see the ONTAP upgrade runbook.
  3. If exploitation is listed as "active", treat remediation as urgent and review exposure (management LIFs, ONTAP S3, SnapMirror endpoints).
  4. Harden in parallel: security hardening baseline and ransomware protection on ONTAP.

Related reading

Browse all ONTAP CVEs → · Security hub