This issue was discovered internally by Arista and the company is not aware of any malicious uses of this issue in customer networks.
Analysis and contextual insights are available on OpenCVE Cloud.
Vendor Solution
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-19640 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.8M 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.
Vendor Workaround
The vulnerability can be mitigated by performing both of the following actions. 1. Kill gNMI subscriptions after AAA authorization policy changes. Run the following command to kill gNMI subscriptions to OpenConfig/Octa on port 6030. If a different port than the default of 6030 is being used for OpenConfig/Octa, adjust accordingly to that port: switch#bash ss -tnp dport = 6030 | grep -o 'pid=[0-9]*' | cut -d= -f2 | xargs sudo kill Note: the port that OpenConfig/Octa is running the gNMI transport on is available in the output of the "show man api gnmi" CLI command (see above under the "Server:" field). 2. Use username and password based authentication (as opposed to mTLS) for gNMI requests to OpenConfig/Octa. The following command is an example using Arista's gNMI client: gnmi -username bob -password myPass123 -addr 127.0.0.1 subscribe /system/state For a transport running mTLS, mTLS can be disabled for this transport by any of the configurations described below: a. Configure the SSL profile to use TLS instead of mTLS. This can be done by removing the trusted certificates from the SSL profile, using the "no trust certificate <name>" CLI command within the SSL profile. For example, if an SSL profile has configuration like: management security ssl profile XXY certificate x.crt key x.key trust certificate A.crt trust certificate B.crt Then this profile can be changed from mTLS to TLS by removing each of the trusted certificates: switch#configure switch(config)#management security switch(config-mgmt-security)#ssl profile XXY switch(config-mgmt-sec-ssl-profile-XXY)#no trust certificate A.crt switch(config-mgmt-sec-ssl-profile-XXY)#no trust certificate B.crt b. Configure the OpenConfig/Octa transport to use an insecure server instead of mTLS, by removing the SSL profile config from the "transport grpc <name>" mode: switch#configure switch(config)#management api gnmi switch(config-mgmt-api-gnmi)#transport grpc default switch(config-gnmi-transport-default)#no ssl profile
Tracking
Sign in to view the affected projects.
No advisories yet.
Wed, 16 Sep 2026 09:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | On affected platforms running Arista EOS, an authenticated user with access to the gNMI (gRPC Network Management Interface) may receive incorrect authorization results, potentially allowing access beyond their currently assigned permissions. This issue was discovered internally by Arista and the company is not aware of any malicious uses of this issue in customer networks. | |
| Title | Security Advisory 0170 | |
| Weaknesses | CWE-863 | |
| References |
| |
| Metrics |
cvssV3_1
|
Subscriptions
No data.
Status: PUBLISHED
Assigner: Arista
Published:
Updated: 2026-09-16T10:13:38.207Z
Reserved: 2026-08-12T16:48:12.259Z
Link: CVE-2026-19640
No data.
Status : Received
Published: 2026-09-16T10:16:50.943
Modified: 2026-09-16T10:16:50.943
Link: CVE-2026-19640
No data.
OpenCVE Enrichment
No data.
-
CWE-863
Incorrect Authorization