CVE-2026-73453 (GCVE-0-2026-73453)
Vulnerability from cvelistv5
Published
2026-09-16 09:46
Modified
2026-09-17 03:56
Severity ?
10.0 (Critical) - CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
9.5 (Critical) - CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
CWE
  • CWE-94 - Improper Control of Generation of Code ('Code Injection')
Summary
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.
References
Impacted products
Vendor Product Version
Arista Networks EOS Version: 4.36.0F   <
Version: 4.35.0F   <
Version: 4.34.0F   <
Version: 4.33.0F   < 4.34.0F
Version: 4.32.0F   < 4.33.0F
Version: 4.31.0F   < 4.32.0F
Version: 4.30.0F   < 4.31.0F
Version: 4.29.2F   < 4.30.0F
 Create a notification for this product.
Show details on NVD website

To clipboard 

{
  "containers": {
    "adp": [
      {
        "metrics": [
          {
            "other": {
              "content": {
                "id": "CVE-2026-73453",
                "options": [
                  {
                    "Exploitation": "none"
                  },
                  {
                    "Automatable": "yes"
                  },
                  {
                    "Technical Impact": "total"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2026-09-16T00:00:00+00:00",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2026-09-17T03:56:37.219Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      }
    ],
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "platforms": [
            "710 Series",
            "720D Series",
            "720XP/722XPM Series",
            "750X Series",
            "7010TX Series",
            "7020R/R4 Series",
            "7130 Series running EOS",
            "7170 Series",
            "7050X3/X4 Series",
            "7060X/X2/X4/X5/X6 Series",
            "7260X/X3 Series",
            "7280R/R2/R3/R4 Series",
            "7300X/X3 Series",
            "7320X Series",
            "7358X4 Series",
            "7368X4 Series",
            "7388X5 Series",
            "7500R/R2/R3 Series",
            "7800R3/R4 Series",
            "7700R4 Series",
            "AWE 5000 Series",
            "AWE 7200R Series",
            "CloudEOS",
            "cEOS-lab",
            "vEOS-lab",
            "CloudVision eXchange, virtual or physical appliance"
          ],
          "product": "EOS",
          "vendor": "Arista Networks",
          "versions": [
            {
              "lessThanOrEqual": "4.36.1F",
              "status": "affected",
              "version": "4.36.0F",
              "versionType": "custom"
            },
            {
              "lessThanOrEqual": "4.35.5M",
              "status": "affected",
              "version": "4.35.0F",
              "versionType": "custom"
            },
            {
              "lessThanOrEqual": "4.34.7M",
              "status": "affected",
              "version": "4.34.0F",
              "versionType": "custom"
            },
            {
              "lessThan": "4.34.0F",
              "status": "affected",
              "version": "4.33.0F",
              "versionType": "custom"
            },
            {
              "lessThan": "4.33.0F",
              "status": "affected",
              "version": "4.32.0F",
              "versionType": "custom"
            },
            {
              "lessThan": "4.32.0F",
              "status": "affected",
              "version": "4.31.0F",
              "versionType": "custom"
            },
            {
              "lessThan": "4.31.0F",
              "status": "affected",
              "version": "4.30.0F",
              "versionType": "custom"
            },
            {
              "lessThan": "4.30.0F",
              "status": "affected",
              "version": "4.29.2F",
              "versionType": "custom"
            }
          ]
        }
      ],
      "configurations": [
        {
          "lang": "en",
          "supportingMedia": [
            {
              "base64": false,
              "type": "text/html",
              "value": "\u003cp\u003eIn order to be vulnerable to CVE-2026-73453, p4-runtime must be configured in one of the following combinations. P4-runtime is not a feature which runs by default and must be explicitly enabled:\u003c/p\u003e\u003cp\u003e1. Non TLS mode (p4-runtime is enabled with no ssl profile configured):\u003c/p\u003e\u003cpre\u003eswitch\u003eshow p4-runtime\nEnabled: yes\nServer: running on port 9559, in mgmtVrf VRF\nSSL profile: none\nAuthentication username priority: x509-spiffe, x509-common-name\nTotal clients: 0\nAccounting requests: no\u003c/pre\u003e\u003cp\u003e2. TLS mode (p4-runtime is enabled and ssl profile is configured with no trusted certificates):\u003c/p\u003e\u003cpre\u003eswitch\u003eshow p4-runtime\nEnabled: yes\nServer: running on port 9559, in mgmtVrf VRF\nSSL profile: campus\nAuthentication username priority: x509-spiffe, x509-common-name\nTotal clients: 0\nAccounting requests: no\u003c/pre\u003e\u003cpre\u003eswitch\u003eshow management security ssl profile campus detail\nProfile: campus\nState: valid\nTrusted certificates: n/a\u003c/pre\u003e\u003cp\u003e3. mTLS mode (p4-runtime is enabled and ssl profile is configured with trusted certificates) + Accounting is enabled for p4-runtime service OR gNSI acctz is enabled + gNSI Authz is disabled:\u003c/p\u003e\u003cpre\u003eswitch\u003eshow p4-runtime\nEnabled: yes\nServer: running on port 9559, in mgmtVrf VRF\nSSL profile: campus\nAuthentication username priority: x509-spiffe, x509-common-name\nTotal clients: 0\nAccounting requests: yes\u003c/pre\u003e\u003cpre\u003eswitch\u003eshow management security ssl profile campus detail\nProfile: campus\nState: valid\nTrusted certificates:\n        - clientRootCa\u003c/pre\u003e\u003cpre\u003eswitch\u003eshow management api gnsi\nTransport: no transport configured\nAcctz enabled: yes\nAttestz enabled: no\nAuthz enabled: no\nCertz enabled: no\nCredentialz enabled: no\nEnrollz enabled: no\nPathz enabled: no\u003c/pre\u003e\u003cp\u003eIf P4Runtime is not configured there is no exposure to this issue:\u003c/p\u003e\u003cpre\u003eswitch\u003eshow p4-runtime\nEnabled: no\u003c/pre\u003e"
            }
          ],
          "value": "In order to be vulnerable to CVE-2026-73453, p4-runtime must be configured in one of the following combinations. P4-runtime is not a feature which runs by default and must be explicitly enabled:\n\n1. Non TLS mode (p4-runtime is enabled with no ssl profile configured):\n\n  switch\u003eshow p4-runtime\n  Enabled: yes\n  Server: running on port 9559, in mgmtVrf VRF\n  SSL profile: none\n  Authentication username priority: x509-spiffe, x509-common-name\n  Total clients: 0\n  Accounting requests: no\n\n2. TLS mode (p4-runtime is enabled and ssl profile is configured with no trusted certificates):\n\n  switch\u003eshow p4-runtime\n  Enabled: yes\n  Server: running on port 9559, in mgmtVrf VRF\n  SSL profile: campus\n  Authentication username priority: x509-spiffe, x509-common-name\n  Total clients: 0\n  Accounting requests: no\n\n  switch\u003eshow management security ssl profile campus detail\n  Profile: campus\n  State: valid\n  Trusted certificates: n/a\n\n3. mTLS mode (p4-runtime is enabled and ssl profile is configured with trusted certificates) + Accounting is enabled for p4-runtime service OR gNSI acctz is enabled + gNSI Authz is disabled:\n\n  switch\u003eshow p4-runtime\n  Enabled: yes\n  Server: running on port 9559, in mgmtVrf VRF\n  SSL profile: campus\n  Authentication username priority: x509-spiffe, x509-common-name\n  Total clients: 0\n  Accounting requests: yes\n\n  switch\u003eshow management security ssl profile campus detail\n  Profile: campus\n  State: valid\n  Trusted certificates:\n          - clientRootCa\n\n  switch\u003eshow management api gnsi\n  Transport: no transport configured\n  Acctz enabled: yes\n  Attestz enabled: no\n  Authz enabled: no\n  Certz enabled: no\n  Credentialz enabled: no\n  Enrollz enabled: no\n  Pathz enabled: no\n\nIf P4Runtime is not configured there is no exposure to this issue:\n\n  switch\u003eshow p4-runtime\n  Enabled: no"
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "supportingMedia": [
            {
              "base64": false,
              "type": "text/html",
              "value": "\u003cp\u003eAn 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.\u003c/p\u003e\u003cp\u003eThis issue was discovered internally by Arista, and the company is not aware of any malicious exploitation of this vulnerability in customer networks.\u003c/p\u003e"
            }
          ],
          "value": "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.\n\nThis issue was discovered internally by Arista, and the company is not aware of any malicious exploitation of this vulnerability in customer networks."
        }
      ],
      "metrics": [
        {
          "cvssV3_1": {
            "baseScore": 10,
            "baseSeverity": "CRITICAL",
            "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H",
            "version": "3.1"
          },
          "format": "CVSS",
          "scenarios": [
            {
              "lang": "en",
              "value": "GENERAL"
            }
          ]
        },
        {
          "cvssV4_0": {
            "baseScore": 9.5,
            "baseSeverity": "CRITICAL",
            "vectorString": "CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H",
            "version": "4.0"
          },
          "format": "CVSS",
          "scenarios": [
            {
              "lang": "en",
              "value": "GENERAL"
            }
          ]
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-94",
              "description": "CWE-94 Improper Control of Generation of Code (\u0027Code Injection\u0027)",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-09-16T10:13:40.303Z",
        "orgId": "c8b34d1a-69ae-45c3-88fe-f3b3d44f39b7",
        "shortName": "Arista"
      },
      "references": [
        {
          "name": "Security Advisory 0174",
          "tags": [
            "vendor-advisory"
          ],
          "url": "https://www.arista.com/en/support/advisories-notices/security-advisory/24730-security-advisory-0174"
        }
      ],
      "solutions": [
        {
          "lang": "en",
          "supportingMedia": [
            {
              "base64": false,
              "type": "text/html",
              "value": "\u003cp\u003eThe 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.\u003c/p\u003e\u003cp\u003eCVE-2026-73453 has been fixed in the following releases:\u003c/p\u003e\u003cul\u003e\u003cli\u003e4.36.2F and later releases in the 4.36.x train\u003c/li\u003e\u003cli\u003e4.35.6M and later releases in the 4.35.x train\u003c/li\u003e\u003cli\u003e4.34.8M and later releases in the 4.34.x train\u003c/li\u003e\u003c/ul\u003e\u003cp\u003eNo hotfix is available for this issue.\u003c/p\u003e"
            }
          ],
          "value": "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.\n\nCVE-2026-73453 has been fixed in the following releases:\n- 4.36.2F and later releases in the 4.36.x train\n- 4.35.6M and later releases in the 4.35.x train\n- 4.34.8M and later releases in the 4.34.x train\n\nNo hotfix is available for this issue."
        }
      ],
      "source": {
        "advisory": "Security Advisory 0174",
        "defects": [
          "BUG 1850014"
        ],
        "discovery": "INTERNAL"
      },
      "title": "Security Advisory 0174",
      "workarounds": [
        {
          "lang": "en",
          "supportingMedia": [
            {
              "base64": false,
              "type": "text/html",
              "value": "\u003cp\u003eTo 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.\u003c/p\u003e\u003cp\u003eBefore implementing this solution, the following pre-requisites must be met:\u003c/p\u003e\u003col\u003e\u003cli\u003eGenerate SPIFFE-ID client certificate signed by the server trusted CA and use it for establishing P4 client connection to the server.\u003c/li\u003e\u003cli\u003eDefine a json file with SPIFFE-ID based policies for Authz service and install it on the device using gNSI Authz.Rotate() rpc.\u003c/li\u003e\u003c/ol\u003e\u003cpre\u003eswitch\u003eshow running-config section p4-runtime\np4-runtime\n   no shutdown\n   !\n   transport grpc foo\n      ssl profile campus\n      authentication username priority x509-spiffe\u003c/pre\u003e\u003cpre\u003eswitch\u003eshow running-config section security\nmanagement security\n   ssl profile campus\n      certificate server.crt key server.key\n      trust certificate ca.crt\u003c/pre\u003e\u003cpre\u003eswitch\u003eshow running-config section gnsi\nmanagement api gnsi\n   service authz\u003c/pre\u003e"
            }
          ],
          "value": "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.\n\nBefore implementing this solution, the following pre-requisites must be met:\n\n1. Generate SPIFFE-ID client certificate signed by the server trusted CA and use it for establishing P4 client connection to the server.\n2. Define a json file with SPIFFE-ID based policies for Authz service and install it on the device using gNSI Authz.Rotate() rpc.\n\n  switch\u003eshow running-config section p4-runtime\n  p4-runtime\n     no shutdown\n     !\n     transport grpc foo\n        ssl profile campus\n        authentication username priority x509-spiffe\n\n  switch\u003eshow running-config section security\n  management security\n     ssl profile campus\n        certificate server.crt key server.key\n        trust certificate ca.crt\n\n  switch\u003eshow running-config section gnsi\n  management api gnsi\n     service authz"
        }
      ]
    }
  },
  "cveMetadata": {
    "assignerOrgId": "c8b34d1a-69ae-45c3-88fe-f3b3d44f39b7",
    "assignerShortName": "Arista",
    "cveId": "CVE-2026-73453",
    "datePublished": "2026-09-16T09:46:33.548Z",
    "dateReserved": "2026-08-12T16:42:47.921Z",
    "dateUpdated": "2026-09-17T03:56:37.219Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "vulnrichment": {
      "containers": "{\"adp\": [{\"title\": \"CISA ADP Vulnrichment\", \"metrics\": [{\"other\": {\"type\": \"ssvc\", \"content\": {\"id\": \"CVE-2026-73453\", \"role\": \"CISA Coordinator\", \"options\": [{\"Exploitation\": \"none\"}, {\"Automatable\": \"yes\"}, {\"Technical Impact\": \"total\"}], \"version\": \"2.0.3\", \"timestamp\": \"2026-09-16T13:41:50.538373Z\"}}}], \"providerMetadata\": {\"orgId\": \"134c704f-9b21-4f2e-91b3-4a467353bcc0\", \"shortName\": \"CISA-ADP\", \"dateUpdated\": \"2026-09-16T13:41:57.151Z\"}}], \"cna\": {\"title\": \"Security Advisory 0174\", \"source\": {\"defects\": [\"BUG 1850014\"], \"advisory\": \"Security Advisory 0174\", \"discovery\": \"INTERNAL\"}, \"metrics\": [{\"format\": \"CVSS\", \"cvssV3_1\": {\"version\": \"3.1\", \"baseScore\": 10, \"baseSeverity\": \"CRITICAL\", \"vectorString\": \"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H\"}, \"scenarios\": [{\"lang\": \"en\", \"value\": \"GENERAL\"}]}, {\"format\": \"CVSS\", \"cvssV4_0\": {\"version\": \"4.0\", \"baseScore\": 9.5, \"baseSeverity\": \"CRITICAL\", \"vectorString\": \"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H\"}, \"scenarios\": [{\"lang\": \"en\", \"value\": \"GENERAL\"}]}], \"affected\": [{\"vendor\": \"Arista Networks\", \"product\": \"EOS\", \"versions\": [{\"status\": \"affected\", \"version\": \"4.36.0F\", \"versionType\": \"custom\", \"lessThanOrEqual\": \"4.36.1F\"}, {\"status\": \"affected\", \"version\": \"4.35.0F\", \"versionType\": \"custom\", \"lessThanOrEqual\": \"4.35.5M\"}, {\"status\": \"affected\", \"version\": \"4.34.0F\", \"versionType\": \"custom\", \"lessThanOrEqual\": \"4.34.7M\"}, {\"status\": \"affected\", \"version\": \"4.33.0F\", \"lessThan\": \"4.34.0F\", \"versionType\": \"custom\"}, {\"status\": \"affected\", \"version\": \"4.32.0F\", \"lessThan\": \"4.33.0F\", \"versionType\": \"custom\"}, {\"status\": \"affected\", \"version\": \"4.31.0F\", \"lessThan\": \"4.32.0F\", \"versionType\": \"custom\"}, {\"status\": \"affected\", \"version\": \"4.30.0F\", \"lessThan\": \"4.31.0F\", \"versionType\": \"custom\"}, {\"status\": \"affected\", \"version\": \"4.29.2F\", \"lessThan\": \"4.30.0F\", \"versionType\": \"custom\"}], \"platforms\": [\"710 Series\", \"720D Series\", \"720XP/722XPM Series\", \"750X Series\", \"7010TX Series\", \"7020R/R4 Series\", \"7130 Series running EOS\", \"7170 Series\", \"7050X3/X4 Series\", \"7060X/X2/X4/X5/X6 Series\", \"7260X/X3 Series\", \"7280R/R2/R3/R4 Series\", \"7300X/X3 Series\", \"7320X Series\", \"7358X4 Series\", \"7368X4 Series\", \"7388X5 Series\", \"7500R/R2/R3 Series\", \"7800R3/R4 Series\", \"7700R4 Series\", \"AWE 5000 Series\", \"AWE 7200R Series\", \"CloudEOS\", \"cEOS-lab\", \"vEOS-lab\", \"CloudVision eXchange, virtual or physical appliance\"], \"defaultStatus\": \"unaffected\"}], \"solutions\": [{\"lang\": \"en\", \"value\": \"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.\\n\\nCVE-2026-73453 has been fixed in the following releases:\\n- 4.36.2F and later releases in the 4.36.x train\\n- 4.35.6M and later releases in the 4.35.x train\\n- 4.34.8M and later releases in the 4.34.x train\\n\\nNo hotfix is available for this issue.\", \"supportingMedia\": [{\"type\": \"text/html\", \"value\": \"\u003cp\u003eThe 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.\u003c/p\u003e\u003cp\u003eCVE-2026-73453 has been fixed in the following releases:\u003c/p\u003e\u003cul\u003e\u003cli\u003e4.36.2F and later releases in the 4.36.x train\u003c/li\u003e\u003cli\u003e4.35.6M and later releases in the 4.35.x train\u003c/li\u003e\u003cli\u003e4.34.8M and later releases in the 4.34.x train\u003c/li\u003e\u003c/ul\u003e\u003cp\u003eNo hotfix is available for this issue.\u003c/p\u003e\", \"base64\": false}]}], \"references\": [{\"url\": \"https://www.arista.com/en/support/advisories-notices/security-advisory/24730-security-advisory-0174\", \"name\": \"Security Advisory 0174\", \"tags\": [\"vendor-advisory\"]}], \"workarounds\": [{\"lang\": \"en\", \"value\": \"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.\\n\\nBefore implementing this solution, the following pre-requisites must be met:\\n\\n1. Generate SPIFFE-ID client certificate signed by the server trusted CA and use it for establishing P4 client connection to the server.\\n2. Define a json file with SPIFFE-ID based policies for Authz service and install it on the device using gNSI Authz.Rotate() rpc.\\n\\n  switch\u003eshow running-config section p4-runtime\\n  p4-runtime\\n     no shutdown\\n     !\\n     transport grpc foo\\n        ssl profile campus\\n        authentication username priority x509-spiffe\\n\\n  switch\u003eshow running-config section security\\n  management security\\n     ssl profile campus\\n        certificate server.crt key server.key\\n        trust certificate ca.crt\\n\\n  switch\u003eshow running-config section gnsi\\n  management api gnsi\\n     service authz\", \"supportingMedia\": [{\"type\": \"text/html\", \"value\": \"\u003cp\u003eTo 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.\u003c/p\u003e\u003cp\u003eBefore implementing this solution, the following pre-requisites must be met:\u003c/p\u003e\u003col\u003e\u003cli\u003eGenerate SPIFFE-ID client certificate signed by the server trusted CA and use it for establishing P4 client connection to the server.\u003c/li\u003e\u003cli\u003eDefine a json file with SPIFFE-ID based policies for Authz service and install it on the device using gNSI Authz.Rotate() rpc.\u003c/li\u003e\u003c/ol\u003e\u003cpre\u003eswitch\u003eshow running-config section p4-runtime\\np4-runtime\\n   no shutdown\\n   !\\n   transport grpc foo\\n      ssl profile campus\\n      authentication username priority x509-spiffe\u003c/pre\u003e\u003cpre\u003eswitch\u003eshow running-config section security\\nmanagement security\\n   ssl profile campus\\n      certificate server.crt key server.key\\n      trust certificate ca.crt\u003c/pre\u003e\u003cpre\u003eswitch\u003eshow running-config section gnsi\\nmanagement api gnsi\\n   service authz\u003c/pre\u003e\", \"base64\": false}]}], \"descriptions\": [{\"lang\": \"en\", \"value\": \"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.\\n\\nThis issue was discovered internally by Arista, and the company is not aware of any malicious exploitation of this vulnerability in customer networks.\", \"supportingMedia\": [{\"type\": \"text/html\", \"value\": \"\u003cp\u003eAn 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.\u003c/p\u003e\u003cp\u003eThis issue was discovered internally by Arista, and the company is not aware of any malicious exploitation of this vulnerability in customer networks.\u003c/p\u003e\", \"base64\": false}]}], \"problemTypes\": [{\"descriptions\": [{\"lang\": \"en\", \"type\": \"CWE\", \"cweId\": \"CWE-94\", \"description\": \"CWE-94 Improper Control of Generation of Code (\u0027Code Injection\u0027)\"}]}], \"configurations\": [{\"lang\": \"en\", \"value\": \"In order to be vulnerable to CVE-2026-73453, p4-runtime must be configured in one of the following combinations. P4-runtime is not a feature which runs by default and must be explicitly enabled:\\n\\n1. Non TLS mode (p4-runtime is enabled with no ssl profile configured):\\n\\n  switch\u003eshow p4-runtime\\n  Enabled: yes\\n  Server: running on port 9559, in mgmtVrf VRF\\n  SSL profile: none\\n  Authentication username priority: x509-spiffe, x509-common-name\\n  Total clients: 0\\n  Accounting requests: no\\n\\n2. TLS mode (p4-runtime is enabled and ssl profile is configured with no trusted certificates):\\n\\n  switch\u003eshow p4-runtime\\n  Enabled: yes\\n  Server: running on port 9559, in mgmtVrf VRF\\n  SSL profile: campus\\n  Authentication username priority: x509-spiffe, x509-common-name\\n  Total clients: 0\\n  Accounting requests: no\\n\\n  switch\u003eshow management security ssl profile campus detail\\n  Profile: campus\\n  State: valid\\n  Trusted certificates: n/a\\n\\n3. mTLS mode (p4-runtime is enabled and ssl profile is configured with trusted certificates) + Accounting is enabled for p4-runtime service OR gNSI acctz is enabled + gNSI Authz is disabled:\\n\\n  switch\u003eshow p4-runtime\\n  Enabled: yes\\n  Server: running on port 9559, in mgmtVrf VRF\\n  SSL profile: campus\\n  Authentication username priority: x509-spiffe, x509-common-name\\n  Total clients: 0\\n  Accounting requests: yes\\n\\n  switch\u003eshow management security ssl profile campus detail\\n  Profile: campus\\n  State: valid\\n  Trusted certificates:\\n          - clientRootCa\\n\\n  switch\u003eshow management api gnsi\\n  Transport: no transport configured\\n  Acctz enabled: yes\\n  Attestz enabled: no\\n  Authz enabled: no\\n  Certz enabled: no\\n  Credentialz enabled: no\\n  Enrollz enabled: no\\n  Pathz enabled: no\\n\\nIf P4Runtime is not configured there is no exposure to this issue:\\n\\n  switch\u003eshow p4-runtime\\n  Enabled: no\", \"supportingMedia\": [{\"type\": \"text/html\", \"value\": \"\u003cp\u003eIn order to be vulnerable to CVE-2026-73453, p4-runtime must be configured in one of the following combinations. P4-runtime is not a feature which runs by default and must be explicitly enabled:\u003c/p\u003e\u003cp\u003e1. Non TLS mode (p4-runtime is enabled with no ssl profile configured):\u003c/p\u003e\u003cpre\u003eswitch\u003eshow p4-runtime\\nEnabled: yes\\nServer: running on port 9559, in mgmtVrf VRF\\nSSL profile: none\\nAuthentication username priority: x509-spiffe, x509-common-name\\nTotal clients: 0\\nAccounting requests: no\u003c/pre\u003e\u003cp\u003e2. TLS mode (p4-runtime is enabled and ssl profile is configured with no trusted certificates):\u003c/p\u003e\u003cpre\u003eswitch\u003eshow p4-runtime\\nEnabled: yes\\nServer: running on port 9559, in mgmtVrf VRF\\nSSL profile: campus\\nAuthentication username priority: x509-spiffe, x509-common-name\\nTotal clients: 0\\nAccounting requests: no\u003c/pre\u003e\u003cpre\u003eswitch\u003eshow management security ssl profile campus detail\\nProfile: campus\\nState: valid\\nTrusted certificates: n/a\u003c/pre\u003e\u003cp\u003e3. mTLS mode (p4-runtime is enabled and ssl profile is configured with trusted certificates) + Accounting is enabled for p4-runtime service OR gNSI acctz is enabled + gNSI Authz is disabled:\u003c/p\u003e\u003cpre\u003eswitch\u003eshow p4-runtime\\nEnabled: yes\\nServer: running on port 9559, in mgmtVrf VRF\\nSSL profile: campus\\nAuthentication username priority: x509-spiffe, x509-common-name\\nTotal clients: 0\\nAccounting requests: yes\u003c/pre\u003e\u003cpre\u003eswitch\u003eshow management security ssl profile campus detail\\nProfile: campus\\nState: valid\\nTrusted certificates:\\n        - clientRootCa\u003c/pre\u003e\u003cpre\u003eswitch\u003eshow management api gnsi\\nTransport: no transport configured\\nAcctz enabled: yes\\nAttestz enabled: no\\nAuthz enabled: no\\nCertz enabled: no\\nCredentialz enabled: no\\nEnrollz enabled: no\\nPathz enabled: no\u003c/pre\u003e\u003cp\u003eIf P4Runtime is not configured there is no exposure to this issue:\u003c/p\u003e\u003cpre\u003eswitch\u003eshow p4-runtime\\nEnabled: no\u003c/pre\u003e\", \"base64\": false}]}], \"providerMetadata\": {\"orgId\": \"c8b34d1a-69ae-45c3-88fe-f3b3d44f39b7\", \"shortName\": \"Arista\", \"dateUpdated\": \"2026-09-16T10:13:40.303Z\"}}}",
      "cveMetadata": "{\"cveId\": \"CVE-2026-73453\", \"state\": \"PUBLISHED\", \"dateUpdated\": \"2026-09-16T13:42:00.799Z\", \"dateReserved\": \"2026-08-12T16:42:47.921Z\", \"assignerOrgId\": \"c8b34d1a-69ae-45c3-88fe-f3b3d44f39b7\", \"datePublished\": \"2026-09-16T09:46:33.548Z\", \"assignerShortName\": \"Arista\"}",
      "dataType": "CVE_RECORD",
      "dataVersion": "5.2"
    }
  }
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.