CVE Alert: CVE-2025-20241 – Cisco – Cisco NX-OS Software
CVE-2025-20241
A vulnerability in the Intermediate System-to-Intermediate System (IS-IS) feature of Cisco NX-OS Software for Cisco Nexus 3000 Series Switches and Cisco Nexus 9000 Series Switches in standalone NX-OS mode could allow an unauthenticated, adjacent attacker to cause the IS-IS process to unexpectedly restart, which could cause an affected device to reload. This vulnerability is due to insufficient input validation when parsing an ingress IS-IS packet. An attacker could exploit this vulnerability by sending a crafted IS-IS packet to an affected device. A successful exploit could allow the attacker to cause the unexpected restart of the IS-IS process, which could cause the affected device to reload, resulting in 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.
AI Summary Analysis
Risk verdict
High risk: an adjacent attacker can trigger a denial-of-service by sending crafted IS-IS packets, potentially causing a device reload.
Why this matters
Unauthenticated, low-effort exploitation could disrupt routing and service availability in networks that rely on Layer 2 IS-IS. In data-centre or large-enterprise fabrics with spine-leaf or core switches, a single reload can propagate outages and impact multiple services.
Most likely attack path
An attacker must be on the same Layer 2 segment to deliver the crafted IS-IS packet. With low complexity and no privileges required, automated testing or broad probing is plausible. If successful, the IS-IS process restarts or the device reboots, causing downtime and potential routing instability across adjacent devices.
Who is most exposed
Networks using IS-IS on core/aggregation switches in data-centre or large-enterprise environments, especially where devices operate in a shared L2 fabric and NX-OS-like modes are deployed.
Detection ideas
- IS-IS process restart or device reboot events logged in syslog.
- Spikes in control-plane CPU/memory coincident with IS-IS traffic surges.
- Unusual IS-IS adjacency flaps or mass SPF recalculations.
- Anomalous IS-IS packet rate or malformed/unexpected LSPs detected by network telemetry.
Mitigation and prioritisation
- Apply vendor-provided patch or upgrade to a fixed NX-OS/Nx-OS-equivalent release; coordinate with change-management and test in a lab before wide rollout.
- If immediate patching isn’t feasible, disable IS-IS where not required, or restrict Layer 2 adjacencies via access controls and segmentation to limit exposure.
- Review and tighten network segmentation (VLANs, isolation of vulnerable devices) and ensure robust backups and a rollback plan.
- Enhance monitoring and alerting for IS-IS process stability, including automated detection of unexpected reboots and routing churn.
- Note: no KEV or EPSS data provided here; monitor for updates and escalate if those indicators change (treat as priority 1 if they indicate high exploitation likelihood).
A considerable amount of time and effort goes into maintaining this website, creating backend automation and creating new features and content for you to make actionable intelligence decisions. Everyone that supports the site helps enable new functionality.
If you like the site, please support us on “Patreon” or “Buy Me A Coffee” using the buttons below
To keep up to date follow us on the below channels.