PoC Monitor
← All CVEs
CVE-2026-73453published 16 Sep 2026 09:46 UTCData: JSON · API

Arista Networks EOS

Security Advisory 0174

An unauthenticated P4Runtime (Programming Protocol-Independent Packet Processors Runtime) client can achieve arbitrary code execution under certain conditions on affected platforms running Arista EOS configured with P4Runtime. P4Runtime is disabled by default in Arista EOS. By crafting a malicious packet during the initiation of a P4Runtime session, an attacker can obtain complete administrative control over the compromised switch. This issue was discovered internally by Arista, and the company is not aware of any malicious exploitation of this vulnerability in customer networks.

First public PoC None yetno public PoC found
Public PoCs00 on GitHub
CVSS10.0critical · scored by CNA · CWE-94
CISA KEV Not listednot known exploited

Affected versions and mitigation

From the CVE record and the vendor's references.

Affected

Arista Networks EOS
  • >= 4.36.0F, <= 4.36.1F
  • >= 4.35.0F, <= 4.35.5M
  • >= 4.34.0F, <= 4.34.7M
  • >= 4.33.0F, < 4.34.0F
  • >= 4.32.0F, < 4.33.0F
  • >= 4.31.0F, < 4.32.0F
  • >= 4.30.0F, < 4.31.0F
  • >= 4.29.2F, < 4.30.0F

Fixed in 4.34.0F, 4.33.0F, 4.32.0F, 4.31.0F, 4.30.0F

Mitigation

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-73453 has been fixed in the following releases: - 4.36.2F 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 No hotfix is available for this issue.

Workaround

To mitigate this issue, it is recommended to configure the p4-runtime service in mTLS mode (ssl profile with trust certificates). Additionally, enable gNSI Authz to facilitate RPC authorization via the client certificate SPIFFE-ID. Please note that enabling mTLS config will terminate all existing P4 client connections and may cause control plane disruption since packet I/O operations are impacted. Before implementing this solution, the following pre-requisites must be met: 1. Generate SPIFFE-ID client certificate signed by the server trusted CA and use it for establishing P4 client connection to the server. 2. Define a json file with SPIFFE-ID based policies for Authz service and install it on the device using gNSI Authz.Rotate() rpc. switch>show running-config section p4-runtime p4-runtime no shutdown ! transport grpc foo ssl profile campus authentication username priority x509-spiffe switch>show running-config section security management security ssl profile campus certificate server.crt key server.key trust certificate ca.crt switch>show running-config section gnsi management api gnsi service authz

References

Timeline

Days relative to CVE publication
-2t=0+2+4+6+8CVE published16 Sep 2026 · t = 0

No public PoC found yet; not in CISA KEV.

PoC repositories

Found on GitHub.

No PoC repositories found yet.