Skip to main content
VulnerabilityPublished

CVE-2026-20074: Cisco IOS XR Software · Improper Validation of Specified Type of Input

Affects Cisco IOS XR SoftwareSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.4 High.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 3.1 base score
7.4High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 4% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 Mar 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
CiscoCisco IOS XR SoftwareAffected
  • 7.8.1 – 25.2.15
32 affected builds
Fixed in–

AI-suggested

To mitigate CVE-2026-20074, organizations should prioritize upgrading affected Cisco IOS XR devices to patched versions provided by Cisco as soon as they become available. Until patches are applied, network administrators should implement strict Layer 2 segmentation and access controls to limit adjacency formation to trusted devices only. Employing features such as port security, dynamic ARP inspection, and DHCP snooping can reduce the risk of unauthorized devices forming adjacencies. Monitoring IS-IS adjacency states and process stability can help detect anomalous behavior indicative of exploitation attempts. Additionally, consider deploying network intrusion detection systems (NIDS) capable of inspecting IS-IS traffic for malformed packets. Network operators should review and harden IS-IS configurations to minimize exposure, including disabling unused IS-IS instances or interfaces where possible. Coordination with Cisco support for guidance on interim workarounds and best practices is recommended. Finally, maintain updated incident response plans to quickly address potential DoS events impacting routing infrastructure.

Description

A vulnerability in the Intermediate System-to-Intermediate System (IS-IS) multi-instance routing feature of Cisco IOS XR Software could allow an unauthenticated, adjacent attacker to cause the IS-IS process to restart unexpectedly. This vulnerability is due to insufficient input validation of ingress IS-IS packets. An attacker could exploit this vulnerability by sending crafted IS-IS packets to an affected device after forming an adjacency. A successful exploit could allow the attacker to cause the IS-IS process to restart unexpectedly, resulting in a temporary loss of connectivity to advertised networks and a denial of service (DoS) condition. Note: The IS-IS protocol is a routing protocol. To exploit this vulnerability, an attacker must be Layer 2-adjacent to the affected device and must have formed an adjacency.  

References

Community reviews

Loading reviews…