CVE-2026-73469 (GCVE-0-2026-73469)
Vulnerability from cvelistv5
Published
2026-09-16 09:55
Modified
2026-09-16 13:41
CWE
  • CWE-863 - Incorrect Authorization
Summary
When specific platforms are using Arista EOS with a loose Unicast Reverse Path Forwarding (uRPF) configuration, certain traffic may not be subjected to the intended verification drop. Consequently, traffic that should be dropped based on these routes could still be processed and forwarded by the device. This issue was discovered internally by Arista and the company is not aware of any malicious uses of this issue in customer networks.
Impacted products
Vendor Product Version
Arista Networks EOS Version: 4.35.0F   <
Create a notification for this product.
Show details on NVD website


{
  "containers": {
    "adp": [
      {
        "metrics": [
          {
            "other": {
              "content": {
                "id": "CVE-2026-73469",
                "options": [
                  {
                    "Exploitation": "none"
                  },
                  {
                    "Automatable": "yes"
                  },
                  {
                    "Technical Impact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2026-09-16T13:41:28.008891Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2026-09-16T13:41:36.781Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      }
    ],
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "platforms": [
            "7050X4 Series",
            "7358X4 Series"
          ],
          "product": "EOS",
          "vendor": "Arista Networks",
          "versions": [
            {
              "lessThanOrEqual": "4.35.4M",
              "status": "affected",
              "version": "4.35.0F",
              "versionType": "custom"
            }
          ]
        }
      ],
      "configurations": [
        {
          "lang": "en",
          "supportingMedia": [
            {
              "base64": false,
              "type": "text/html",
              "value": "\u003cp\u003eIn order to be vulnerable to CVE-2026-73469, loose mode uRPF must be configured on an interface. This can be checked by showing the interface status, or by checking the current switch config.\u003c/p\u003e\u003cpre\u003eswitch\u003eshow ip interface\nEthernet1/1 is up, line protocol is up (connected)\n  Internet address is 192.0.2.1/24\n  ...\n  IP verify unicast source reachable-via any\n  ...\u003c/pre\u003e\u003cpre\u003eswitch\u003eshow ipv6 interface\nEthernet1/1 is up, line protocol is up (connected)\n  ...\n  IPv6 verify unicast source reachable-via any\n  ...\u003c/pre\u003e\u003cpre\u003eswitch\u003eshow running-config section ip verify\ninterface Ethernet1/1\n   ip verify unicast source reachable-via any\u003c/pre\u003e\u003cpre\u003eswitch\u003eshow running-config section ipv6 verify\ninterface Ethernet1/1\n   ipv6 verify unicast source reachable-via any\u003c/pre\u003e\u003cp\u003eIf loose mode uRPF is not configured on an interface, there is no exposure to this issue. In this example, Ethernet1/1 is configured with strict mode uRPF (reachable-via RX), and Ethernet2/1 is not configured with any uRPF \u2014 neither are affected:\u003c/p\u003e\u003cpre\u003eswitch\u003eshow ip interface\nEthernet1/1 is up, line protocol is up (connected)\n  Internet address is 192.0.2.1/24\n  ...\n  IP verify unicast source reachable-via RX\n  ...\nEthernet2/1 is up, line protocol is up (connected)\n  Internet address is 198.51.100.1/24\n  ...\u003c/pre\u003e"
            }
          ],
          "value": "In order to be vulnerable to CVE-2026-73469, loose mode uRPF must be configured on an interface. This can be checked by showing the interface status, or by checking the current switch config.\n\n  switch\u003eshow ip interface\n  Ethernet1/1 is up, line protocol is up (connected)\n    Internet address is 192.0.2.1/24\n    ...\n    IP verify unicast source reachable-via any\n    ...\n\n  switch\u003eshow ipv6 interface\n  Ethernet1/1 is up, line protocol is up (connected)\n    ...\n    IPv6 verify unicast source reachable-via any\n    ...\n\n  switch\u003eshow running-config section ip verify\n  interface Ethernet1/1\n     ip verify unicast source reachable-via any\n\n  switch\u003eshow running-config section ipv6 verify\n  interface Ethernet1/1\n     ipv6 verify unicast source reachable-via any\n\nIf loose mode uRPF is not configured on an interface, there is no exposure to this issue. In this example, Ethernet1/1 is configured with strict mode uRPF (reachable-via RX), and Ethernet2/1 is not configured with any uRPF \u2014 neither are affected:\n\n  switch\u003eshow ip interface\n  Ethernet1/1 is up, line protocol is up (connected)\n    Internet address is 192.0.2.1/24\n    ...\n    IP verify unicast source reachable-via RX\n    ...\n  Ethernet2/1 is up, line protocol is up (connected)\n    Internet address is 198.51.100.1/24\n    ..."
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "supportingMedia": [
            {
              "base64": false,
              "type": "text/html",
              "value": "\u003cp\u003eWhen specific platforms are using Arista EOS with a loose Unicast Reverse Path Forwarding (uRPF) configuration, certain traffic may not be subjected to the intended verification drop. Consequently, traffic that should be dropped based on these routes could still be processed and forwarded by the device.\u003c/p\u003e\u003cp\u003eThis issue was discovered internally by Arista and the company is not aware of any malicious uses of this issue in customer networks.\u003c/p\u003e"
            }
          ],
          "value": "When specific platforms are using Arista EOS with a loose Unicast Reverse Path Forwarding (uRPF) configuration, certain traffic may not be subjected to the intended verification drop. Consequently, traffic that should be dropped based on these routes could still be processed and forwarded by the device.\n\nThis issue was discovered internally by Arista and the company is not aware of any malicious uses of this issue in customer networks."
        }
      ],
      "metrics": [
        {
          "cvssV3_1": {
            "baseScore": 5.8,
            "baseSeverity": "MEDIUM",
            "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:L/A:N",
            "version": "3.1"
          },
          "format": "CVSS",
          "scenarios": [
            {
              "lang": "en",
              "value": "GENERAL"
            }
          ]
        },
        {
          "cvssV4_0": {
            "baseScore": 6.9,
            "baseSeverity": "MEDIUM",
            "vectorString": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N",
            "version": "4.0"
          },
          "format": "CVSS",
          "scenarios": [
            {
              "lang": "en",
              "value": "GENERAL"
            }
          ]
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-863",
              "description": "CWE-863 Incorrect Authorization",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-09-16T10:13:40.801Z",
        "orgId": "c8b34d1a-69ae-45c3-88fe-f3b3d44f39b7",
        "shortName": "Arista"
      },
      "references": [
        {
          "name": "Security Advisory 0176",
          "tags": [
            "vendor-advisory"
          ],
          "url": "https://www.arista.com/en/support/advisories-notices/security-advisory/24732-security-advisory-0176"
        }
      ],
      "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-73469 has been fixed in the following releases:\u003c/p\u003e\u003cul\u003e\u003cli\u003e4.36.0F and later releases in the 4.36.x train\u003c/li\u003e\u003cli\u003e4.35.5M and later releases in the 4.35.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-73469 has been fixed in the following releases:\n- 4.36.0F and later releases in the 4.36.x train\n- 4.35.5M and later releases in the 4.35.x train\n\nNo hotfix is available for this issue."
        }
      ],
      "source": {
        "advisory": "Security Advisory 0176",
        "defects": [
          "BUG 1353206"
        ],
        "discovery": "INTERNAL"
      },
      "title": "Security Advisory 0176",
      "workarounds": [
        {
          "lang": "en",
          "supportingMedia": [
            {
              "base64": false,
              "type": "text/html",
              "value": "\u003cp\u003eNo mitigation exists for this issue.\u003c/p\u003e"
            }
          ],
          "value": "No mitigation exists for this issue."
        }
      ]
    }
  },
  "cveMetadata": {
    "assignerOrgId": "c8b34d1a-69ae-45c3-88fe-f3b3d44f39b7",
    "assignerShortName": "Arista",
    "cveId": "CVE-2026-73469",
    "datePublished": "2026-09-16T09:55:14.065Z",
    "dateReserved": "2026-08-12T16:47:18.121Z",
    "dateUpdated": "2026-09-16T13:41:36.781Z",
    "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-73469\", \"role\": \"CISA Coordinator\", \"options\": [{\"Exploitation\": \"none\"}, {\"Automatable\": \"yes\"}, {\"Technical Impact\": \"partial\"}], \"version\": \"2.0.3\", \"timestamp\": \"2026-09-16T13:41:28.008891Z\"}}}], \"providerMetadata\": {\"orgId\": \"134c704f-9b21-4f2e-91b3-4a467353bcc0\", \"shortName\": \"CISA-ADP\", \"dateUpdated\": \"2026-09-16T13:41:32.256Z\"}}], \"cna\": {\"title\": \"Security Advisory 0176\", \"source\": {\"defects\": [\"BUG 1353206\"], \"advisory\": \"Security Advisory 0176\", \"discovery\": \"INTERNAL\"}, \"metrics\": [{\"format\": \"CVSS\", \"cvssV3_1\": {\"version\": \"3.1\", \"baseScore\": 5.8, \"baseSeverity\": \"MEDIUM\", \"vectorString\": \"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:L/A:N\"}, \"scenarios\": [{\"lang\": \"en\", \"value\": \"GENERAL\"}]}, {\"format\": \"CVSS\", \"cvssV4_0\": {\"version\": \"4.0\", \"baseScore\": 6.9, \"baseSeverity\": \"MEDIUM\", \"vectorString\": \"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N\"}, \"scenarios\": [{\"lang\": \"en\", \"value\": \"GENERAL\"}]}], \"affected\": [{\"vendor\": \"Arista Networks\", \"product\": \"EOS\", \"versions\": [{\"status\": \"affected\", \"version\": \"4.35.0F\", \"versionType\": \"custom\", \"lessThanOrEqual\": \"4.35.4M\"}], \"platforms\": [\"7050X4 Series\", \"7358X4 Series\"], \"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-73469 has been fixed in the following releases:\\n- 4.36.0F and later releases in the 4.36.x train\\n- 4.35.5M and later releases in the 4.35.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-73469 has been fixed in the following releases:\u003c/p\u003e\u003cul\u003e\u003cli\u003e4.36.0F and later releases in the 4.36.x train\u003c/li\u003e\u003cli\u003e4.35.5M and later releases in the 4.35.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/24732-security-advisory-0176\", \"name\": \"Security Advisory 0176\", \"tags\": [\"vendor-advisory\"]}], \"workarounds\": [{\"lang\": \"en\", \"value\": \"No mitigation exists for this issue.\", \"supportingMedia\": [{\"type\": \"text/html\", \"value\": \"\u003cp\u003eNo mitigation exists for this issue.\u003c/p\u003e\", \"base64\": false}]}], \"descriptions\": [{\"lang\": \"en\", \"value\": \"When specific platforms are using Arista EOS with a loose Unicast Reverse Path Forwarding (uRPF) configuration, certain traffic may not be subjected to the intended verification drop. Consequently, traffic that should be dropped based on these routes could still be processed and forwarded by the device.\\n\\nThis issue was discovered internally by Arista and the company is not aware of any malicious uses of this issue in customer networks.\", \"supportingMedia\": [{\"type\": \"text/html\", \"value\": \"\u003cp\u003eWhen specific platforms are using Arista EOS with a loose Unicast Reverse Path Forwarding (uRPF) configuration, certain traffic may not be subjected to the intended verification drop. Consequently, traffic that should be dropped based on these routes could still be processed and forwarded by the device.\u003c/p\u003e\u003cp\u003eThis issue was discovered internally by Arista and the company is not aware of any malicious uses of this issue in customer networks.\u003c/p\u003e\", \"base64\": false}]}], \"problemTypes\": [{\"descriptions\": [{\"lang\": \"en\", \"type\": \"CWE\", \"cweId\": \"CWE-863\", \"description\": \"CWE-863 Incorrect Authorization\"}]}], \"configurations\": [{\"lang\": \"en\", \"value\": \"In order to be vulnerable to CVE-2026-73469, loose mode uRPF must be configured on an interface. This can be checked by showing the interface status, or by checking the current switch config.\\n\\n  switch\u003eshow ip interface\\n  Ethernet1/1 is up, line protocol is up (connected)\\n    Internet address is 192.0.2.1/24\\n    ...\\n    IP verify unicast source reachable-via any\\n    ...\\n\\n  switch\u003eshow ipv6 interface\\n  Ethernet1/1 is up, line protocol is up (connected)\\n    ...\\n    IPv6 verify unicast source reachable-via any\\n    ...\\n\\n  switch\u003eshow running-config section ip verify\\n  interface Ethernet1/1\\n     ip verify unicast source reachable-via any\\n\\n  switch\u003eshow running-config section ipv6 verify\\n  interface Ethernet1/1\\n     ipv6 verify unicast source reachable-via any\\n\\nIf loose mode uRPF is not configured on an interface, there is no exposure to this issue. In this example, Ethernet1/1 is configured with strict mode uRPF (reachable-via RX), and Ethernet2/1 is not configured with any uRPF \\u2014 neither are affected:\\n\\n  switch\u003eshow ip interface\\n  Ethernet1/1 is up, line protocol is up (connected)\\n    Internet address is 192.0.2.1/24\\n    ...\\n    IP verify unicast source reachable-via RX\\n    ...\\n  Ethernet2/1 is up, line protocol is up (connected)\\n    Internet address is 198.51.100.1/24\\n    ...\", \"supportingMedia\": [{\"type\": \"text/html\", \"value\": \"\u003cp\u003eIn order to be vulnerable to CVE-2026-73469, loose mode uRPF must be configured on an interface. This can be checked by showing the interface status, or by checking the current switch config.\u003c/p\u003e\u003cpre\u003eswitch\u003eshow ip interface\\nEthernet1/1 is up, line protocol is up (connected)\\n  Internet address is 192.0.2.1/24\\n  ...\\n  IP verify unicast source reachable-via any\\n  ...\u003c/pre\u003e\u003cpre\u003eswitch\u003eshow ipv6 interface\\nEthernet1/1 is up, line protocol is up (connected)\\n  ...\\n  IPv6 verify unicast source reachable-via any\\n  ...\u003c/pre\u003e\u003cpre\u003eswitch\u003eshow running-config section ip verify\\ninterface Ethernet1/1\\n   ip verify unicast source reachable-via any\u003c/pre\u003e\u003cpre\u003eswitch\u003eshow running-config section ipv6 verify\\ninterface Ethernet1/1\\n   ipv6 verify unicast source reachable-via any\u003c/pre\u003e\u003cp\u003eIf loose mode uRPF is not configured on an interface, there is no exposure to this issue. In this example, Ethernet1/1 is configured with strict mode uRPF (reachable-via RX), and Ethernet2/1 is not configured with any uRPF \\u2014 neither are affected:\u003c/p\u003e\u003cpre\u003eswitch\u003eshow ip interface\\nEthernet1/1 is up, line protocol is up (connected)\\n  Internet address is 192.0.2.1/24\\n  ...\\n  IP verify unicast source reachable-via RX\\n  ...\\nEthernet2/1 is up, line protocol is up (connected)\\n  Internet address is 198.51.100.1/24\\n  ...\u003c/pre\u003e\", \"base64\": false}]}], \"providerMetadata\": {\"orgId\": \"c8b34d1a-69ae-45c3-88fe-f3b3d44f39b7\", \"shortName\": \"Arista\", \"dateUpdated\": \"2026-09-16T10:13:40.801Z\"}}}",
      "cveMetadata": "{\"cveId\": \"CVE-2026-73469\", \"state\": \"PUBLISHED\", \"dateUpdated\": \"2026-09-16T13:41:36.781Z\", \"dateReserved\": \"2026-08-12T16:47:18.121Z\", \"assignerOrgId\": \"c8b34d1a-69ae-45c3-88fe-f3b3d44f39b7\", \"datePublished\": \"2026-09-16T09:55:14.065Z\", \"assignerShortName\": \"Arista\"}",
      "dataType": "CVE_RECORD",
      "dataVersion": "5.2"
    }
  }
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

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.


Loading…

Loading…