Home / Security / Advisories / NTAP-20260422-0005

NTAP-20260422-0005 — CVE-2026-33186 gRPC-Go Vulnerability in NetApp Products

Published 2026-04-22 · Updated 2026-08-19 · Status: Interim · Exploitation: Public · Severity: CRITICAL 9.1 · ONTAP affected: Yes

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

Product family: ONTAP · Astra Control · NetApp Console / BlueXP · SolidFire / NetApp HCI | ONTAP-relevant | highest CVSS: 9.1

CVEs in this advisory

CVE-2026-33186 — CRITICAL · CVSS 9.1 · site index

What the CVE records say

CVE-2026-33186 — gRPC-Go is the Go language implementation of gRPC. Versions prior to 1.79.3 have an authorization bypass resulting from improper input validation of the HTTP/2 `:path` pseudo-header. The gRPC-Go server was too lenient in its routing logic, accepting requests where the `:path` omitted the mandatory leading slash (e.g., `Service/Method` instead of `/Service/Method`). While the server successfully routed these requests to the correct handler, authorization interceptors (including the official `grpc/authz` package) evaluated the raw, non-canonical path string. Consequently, "deny" rules defined using canonical paths (starting with `/`) failed to match the incoming request, allowing it to bypass the policy if a fallback "allow" rule was present. This affects gRPC-Go servers that use path-based authorization interceptors, such as the official RBAC implementation in `google.golang.org/grpc/authz` or custom interceptors relying on `info.FullMethod` or `grpc.Method(ctx)`; AND that have a security policy contains specific "deny" rules for canonical paths but allows other requests by default (a fallback "allow" rule). The vulnerability is exploitable by an attacker who can send raw HTTP/2 frames with malformed `:path` headers directly to the gRPC server. The fix in version 1.79.3 ensures that any request with a `:path` that does not start with a leading slash is immediately rejected with a `codes.Unimplemented` error, preventing it from reaching authorization interceptors or handlers with a non-canonical path string. While upgrading is the most secure and recommended path, users can mitigate the vulnerability using one of the following methods: Use a validating interceptor (recommended mitigation); infrastructure-level normalization; and/or policy hardening.

Impact

Successful exploitation of this vulnerability could lead to disclosure of sensitive information or addition or modification of data.

Affected products

ONTAP tools for VMware vSphere 10
Astra Control Provisioner
NetApp Console Agent
NetApp Console Agent OVA
NetApp SolidFire & HCI Management Node
NetApp SolidFire & HCI Storage Node (Element Software)
Terraform Provider for ONTAP

Official fixes

ONTAP tools for VMware vSphere 10 — vendor fix ↗

References

https://github.com/grpc/grpc-go/security/advisories/GHSA-p77j-4mvh-x3m3 ↗

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.