On affected platforms running Arista EOS, when multiple gRPC Network Security Interface (gNSI) transports are configured, a race condition in the gNSI Authz service may cause a policy rotation to fail silently. An authenticated user whose access was revoked by the new policy may retain unauthorized access to gRPC interfaces. This does not affect Bootz.
This issue was discovered internally by Arista, and the company is not aware of any malicious exploitation of this vulnerability in customer networks.
In order to be vulnerable to CVE-2026-73463, gNSI Authz must be enabled with multiple transports configured:
switch#show man api gnsi
Transport: default
Transport enabled: yes
Server: running on port 6030, in default VRF
Transport: other
Transport enabled: yes
Server: running on port 6031, in default VRF
Acctz enabled: no
Attestz enabled: no
Authz enabled: yes
Certz enabled: no
Credentialz enabled: no
Enrollz enabled: no
Pathz enabled: no
Please note that a system may have been affected by this vulnerability if a secondary transport (such as the "other" transport in the preceding example) was configured at any point. The running configuration on the system may have subsequently been modified to remove this secondary transport.
Restrict the set of users that can enable gNSI on OpenConfig / Octa transports via the CLI.
Firstly, configure AAA authorization. The following is an example of configuring AAA authorization for all privilege levels using only the local user database:
switch(config)#aaa authorization commands all default local
switch(config)#aaa authorization config-commands
Now restrict a sufficient subset of all roles from enabling gNSI services. In the below example, we prohibit just network-operators:
switch(config-mgmt-api-gnsi)#role network-operator
switch(config-role-network-operator)#10 deny mode mgmt-api-gnsi command transport gnmi .
256 permit command .
The recommended resolution is to upgrade to a remediated software version at your earliest convenience. Arista recommends customers move to the latest version of each release that contains all the fixes listed below.
CVE-2026-73463 has been fixed in the following releases:
- 4.36.1F and later releases in the 4.36.x train
- 4.35.6M and later releases in the 4.35.x train
- 4.34.7.1M and later releases in the 4.34.x train
- 4.33.9M and later releases in the 4.33.x train
No hotfix is available for this issue.