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.
Published: 2026-09-16
Score: 2.3 Low
EPSS: < 1% Very Low
KEV: No
Impact: Privilege Escalation via gNMI authorization flaw
Action: Patch immediately
AI Analysis

Impact

On Arista EOS platforms an authenticated user that accesses the gNMI service may permissions in excess of those they are configured for, allowing execution of commands or viewing of information beyond the user’s intended scope. The flaw is caused by an incorrect authorization decision implementation (CWE-863) and results in a potential elevation of privileges.

Affected Systems

Affected devices run Arista Networks EOS. Firmware versions prior to the following mitigations are vulnerable: 4.36.0F and earlier in the 4.36.x train, 4.35.5M and earlier in the 4.35.x train, 4.34.7M and earlier in the 4.34.x train, and 4.33.8M and earlier in the 4.33.x train. Upgrading to 4.36.1F or any later release in the 4.36.x train, 4.35.6M or later in the 4.35.x train, 4.34.8.34.x train, or 4.33.9M or later in the 4.33.x train resolves the issue.

Risk and Exploitability

The CVSS base score is 2.3, indicating low technical severity, and there is no EPSS data available. The vulnerability is not listed in the CISA KEV catalog. Exploitation requires authenticated access to gNMI, and the attacker must either control or be able to modify AAA authorization policies. Likely attack vectors include remote gNMI connections over the default port 6030 or other configured gNMI ports, using either mutual TLS or username/password authentication. Because the flaw yields incorrect privilege checks, recovery of the correct authorization state would require reapplying the correct policy after any change.

Generated by OpenCVE AI on September 16, 2026 at 13:22 UTC.

Remediation

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


OpenCVE Recommended Actions

  • Upgrade the EOS firmware to 4.36.1F or any later release in the 4.36.x train, 4.35.6M or later in the 4.35.x train, 4.34.8M or later in the 4.34.x train,M or later in the 4.33.x train.
  • If an immediate upgrade is not possible, execute the workaround by killing all gNMI subscriptions to OpenConfig/Octa after AAA policy changes using the provided kill command and by switching the gNMI transport to use username/password authentication instead of mutual TLS.
  • Adjust the SSL profile for the gNMI transport to employ TLS or an insecure server instead of mTLS by removing trusted certificates or disabling the SSL profile entirely as described in the advisory.

Generated by OpenCVE AI on September 16, 2026 at 13:22 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Wed, 16 Sep 2026 14:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


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

{'score': 4.2, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N'}

cvssV4_0

{'score': 2.3, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N'}


Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: Arista

Published:

Updated: 2026-09-16T13:57:56.343Z

Reserved: 2026-08-12T16:48:12.259Z

Link: CVE-2026-19640

cve-icon Vulnrichment

Updated: 2026-09-16T13:55:11.620Z

cve-icon NVD

Status : Awaiting Analysis

Published: 2026-09-16T10:16:50.943

Modified: 2026-09-16T19:08:50.420

Link: CVE-2026-19640

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-09-16T13:30:10Z

Weaknesses