On affected platforms running Arista EOS with gRPC Network Management Interface (gNMI) enabled, a specially crafted request could allow a malicious authenticated client with gRPC Network Management Interface (gNMI) access to execute arbitrary code with root privileges on the switch.
In order to be vulnerable to CVE-2026-73464, the following condition must be met:
gNMI transport must be enabled:
switch(config)#show management api gnmi
Transport: default
Enabled: yes
Server: running on port 6030, in default VRF
SSL profile: none
QoS DSCP: none
Connection limit: 100
Authorization required: no
Accounting requests: no
Notification timestamp: last change time
Listen addresses: ::
Authentication username priority: x509-spiffe, metadata, x509-common-name
Config-commands AAA accounting: enabled
Config-commands AAA authorization: enabled
If a gNMI transport is not configured there is no exposure to this issue and the message will look something like:
switch(config)#show management api gnmi
Enabled: no transports enabled
Disable any gNMI transports:
management api gnmi
no transport grpc <name>
Disabling all gNMI transports makes gNMI, gNOI, and gNSI services unavailable. If no RESTCONF or NETCONF transports are configured, the OpenConfig/Octa agent will also stop. CloudVision provisioning via TerminAttr is unaffected. All services resume when a gNMI transport is re-enabled.
Note: This mitigation is not applicable to DMF-managed EOS switches. gNMI transports are enabled by default on these platforms and cannot be disabled.
The following EOS releases contain the fix for this vulnerability:
- 4.33.9M and later releases in the 4.33.x train
- 4.34.7.1M and later releases in the 4.34.x train
- 4.35.6M and later releases in the 4.35.x train
- 4.36.1F and later releases in the 4.36.x train
No hotfix is available for this vulnerability.