Description
On affected platforms running Arista EOS, if OpenConfig is configured and running a gNMI server on the system, and if gNSI Pathz is configured and a gNSI Pathz policy is present on the system, then gNMI may fail to correctly enforce the rules in this policy if both a group rule and a user rule for the same path is present in the policy. Under certain conditions, this can lead to an authenticated user gaining unauthorized permission to read or write gNMI paths that the Pathz policy is intended to restrict.
Published: 2026-09-16
Score: 7.7 High
EPSS: < 1% Very Low
KEV: No
Impact: Unauthorized access to gNMI data
Action: Immediate Patch
AI Analysis

Impact

The vulnerability allows a gNMI client to bypass security rules defined in a gNSI Pathz policy when both a group rule and a user rule reference the same path. Because the policy engine performs an incorrect comparison, the best‑matched rule is not applied and the request may be permitted. This flaw can enable an authenticated user to read or modify gNMI data that was supposed to be restricted, violating confidentiality and integrity of the device configuration and operational data.

Affected Systems

Arista Networks’ EOS operating system is affected. EOS versions older than 4.33.9M, 4.34.7M, 4.35.6M, and 4.36.1F contain the flaw. A system that has OpenConfig enabled, runs a gNMI server, and has at least one non‑empty gNSI Pathz policy in place is at risk.

Risk and Exploitability

The CVSS score of 7.7 reflects high severity. The EPSS score of less than 1% indicates that exploitation is currently unlikely, and the vulnerability is not listed in CISA’s KEV catalog. Nevertheless, exploitation is straightforward for an attacker who can authenticate to the gNMI API and has knowledge of a policy that includes both group and user rules for the same path. The flaw requires no special privilege escalation beyond the existing gNMI session, making the attack path simple and the risk tangible when the conditions are met.

Generated by OpenCVE AI on September 16, 2026 at 14:55 UTC.

Remediation

Vendor Solution

The following EOS releases contain the fix for this vulnerability: - 4.33.9M and later releases in the 4.33.x train - 4.34.7M 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.


Vendor Workaround

Option 1: Disable gNSI Pathz entirely: switch#configure switch(config)#management api gnsi switch(config-mgmt-api-gnsi)#no service pathz Option 2: Push a new gNSI Pathz policy that does not contain any group rules, using only user-principal rules. To push a new policy via grpcurl: grpcurl -protoset ./pathz.proto.pb -H 'username:$USER' -v -d @ -plaintext $TARGET:$PORT gnsi.pathz.v1.Pathz/Rotate << EOF { "upload_request": { "version": "<version>", "created_on": <timestamp>, "policy": <policy> } } { "finalize_rotation": {} } EOF Ensure all rules in the policy use "user" as the principal rather than "group" to avoid triggering this vulnerability.


OpenCVE Recommended Actions

  • Upgrade the EOS image to a patched release: 4.33.9M or later in the 4.33 train, 4.34.7M or later in the 4.34 train, 4.35.6M or later in the 4.35 train, or 4.36.1F or later in the 4.36 train.
  • If an upgrade is delayed, disable the Pathz service completely by entering the EOS configuration prompt and executing "no service pathz" under the management‑api‑gnsi configuration hierarchy.
  • Re‑configure any existing Pathz policy so that it contains only user‑principal rules, removing or converting any group rules that target the same path.
  • If OpenConfig or the gNMI server are not required, consider disabling them to eliminate the attack surface.

Generated by OpenCVE AI on September 16, 2026 at 14:55 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

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

Type Values Removed Values Added
Metrics ssvc

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


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

Type Values Removed Values Added
Description On affected platforms running Arista EOS, if OpenConfig is configured and running a gNMI server on the system, and if gNSI Pathz is configured and a gNSI Pathz policy is present on the system, then gNMI may fail to correctly enforce the rules in this policy if both a group rule and a user rule for the same path is present in the policy. Under certain conditions, this can lead to an authenticated user gaining unauthorized permission to read or write gNMI paths that the Pathz policy is intended to restrict.
Title Security Advisory 0164
Weaknesses CWE-842
References
Metrics cvssV3_1

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

cvssV4_0

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


Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: Arista

Published:

Updated: 2026-09-17T03:56:54.834Z

Reserved: 2026-08-12T16:39:35.977Z

Link: CVE-2026-73439

cve-icon Vulnrichment

Updated: 2026-09-16T14:51:54.812Z

cve-icon NVD

Status : Awaiting Analysis

Published: 2026-09-16T09:17:04.687

Modified: 2026-09-17T04:17:59.307

Link: CVE-2026-73439

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-09-16T15:00:07Z

Weaknesses
  • CWE-842

    Placement of User into Incorrect Group