CVE-2026-73469 (GCVE-0-2026-73469)

Vulnerability from cvelistv5 – Published: 2026-09-16 09:55 – Updated: 2026-09-16 13:41
VLAI
Title
Security Advisory 0176
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.
SSVC
Exploitation: none Automatable: yes Technical Impact: partial
CISA Coordinator · CISA-ADP (v2.0.3)
Decision recorded 2026-09-16 13:41 UTC
CWE
  • CWE-863 - Incorrect Authorization
Assigner
Arista CNA under the mitre root
CNA scorecard B 87/100 over 116 records in the last 180 days details
References
Impacted products
Vendor Product Version CPE status
Arista Networks EOS Affected: 4.35.0F , ≤ 4.35.4M (custom)
guessed 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": {
    "epss": {
      "cve": "CVE-2026-73469",
      "date": "2026-11-15",
      "epss": "0.00294",
      "percentile": "0.22269"
    },
    "nvd": {
      "cve": {
        "affected": [
          {
            "affectedData": [
              {
                "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"
                  }
                ]
              }
            ],
            "source": "psirt@arista.com"
          }
        ],
        "cveTags": [],
        "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."
          }
        ],
        "id": "CVE-2026-73469",
        "lastModified": "2026-09-16T19:08:50.420",
        "metrics": {
          "cvssMetricV31": [
            {
              "cvssData": {
                "attackComplexity": "LOW",
                "attackVector": "NETWORK",
                "availabilityImpact": "NONE",
                "baseScore": 5.8,
                "baseSeverity": "MEDIUM",
                "confidentialityImpact": "NONE",
                "integrityImpact": "LOW",
                "privilegesRequired": "NONE",
                "scope": "CHANGED",
                "userInteraction": "NONE",
                "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:L/A:N",
                "version": "3.1"
              },
              "exploitabilityScore": 3.9,
              "impactScore": 1.4,
              "source": "psirt@arista.com",
              "type": "Secondary"
            }
          ],
          "cvssMetricV40": [
            {
              "cvssData": {
                "Automatable": "NOT_DEFINED",
                "Recovery": "NOT_DEFINED",
                "Safety": "NOT_DEFINED",
                "attackComplexity": "LOW",
                "attackRequirements": "NONE",
                "attackVector": "NETWORK",
                "availabilityRequirement": "NOT_DEFINED",
                "baseScore": 6.9,
                "baseSeverity": "MEDIUM",
                "confidentialityRequirement": "NOT_DEFINED",
                "exploitMaturity": "NOT_DEFINED",
                "integrityRequirement": "NOT_DEFINED",
                "modifiedAttackComplexity": "NOT_DEFINED",
                "modifiedAttackRequirements": "NOT_DEFINED",
                "modifiedAttackVector": "NOT_DEFINED",
                "modifiedPrivilegesRequired": "NOT_DEFINED",
                "modifiedSubAvailabilityImpact": "NOT_DEFINED",
                "modifiedSubConfidentialityImpact": "NOT_DEFINED",
                "modifiedSubIntegrityImpact": "NOT_DEFINED",
                "modifiedUserInteraction": "NOT_DEFINED",
                "modifiedVulnAvailabilityImpact": "NOT_DEFINED",
                "modifiedVulnConfidentialityImpact": "NOT_DEFINED",
                "modifiedVulnIntegrityImpact": "NOT_DEFINED",
                "privilegesRequired": "NONE",
                "providerUrgency": "NOT_DEFINED",
                "subAvailabilityImpact": "NONE",
                "subConfidentialityImpact": "NONE",
                "subIntegrityImpact": "NONE",
                "userInteraction": "NONE",
                "valueDensity": "NOT_DEFINED",
                "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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X",
                "version": "4.0",
                "vulnAvailabilityImpact": "NONE",
                "vulnConfidentialityImpact": "NONE",
                "vulnIntegrityImpact": "LOW",
                "vulnerabilityResponseEffort": "NOT_DEFINED"
              },
              "source": "psirt@arista.com",
              "type": "Secondary"
            }
          ],
          "ssvcV203": [
            {
              "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
              "ssvcData": {
                "id": "CVE-2026-73469",
                "options": [
                  {
                    "exploitation": "none"
                  },
                  {
                    "automatable": "yes"
                  },
                  {
                    "technicalImpact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2026-09-16T13:41:28.008891Z",
                "version": "2.0.3"
              }
            }
          ]
        },
        "published": "2026-09-16T10:16:52.510",
        "references": [
          {
            "source": "psirt@arista.com",
            "url": "https://www.arista.com/en/support/advisories-notices/security-advisory/24732-security-advisory-0176"
          }
        ],
        "sourceIdentifier": "psirt@arista.com",
        "vulnStatus": "Awaiting Analysis",
        "weaknesses": [
          {
            "description": [
              {
                "lang": "en",
                "value": "CWE-863"
              }
            ],
            "source": "psirt@arista.com",
            "type": "Secondary"
          }
        ]
      }
    },
    "vulnrichment": {
      "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:32.256Z",
              "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"
    }
  }
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Events included in the timeline

Loading timeline…


    Loading…

    Loading…

    Loading…

    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.