Skip to main content
VulnerabilityPublished

CVE-2025-20315: Cisco IOS XE Software · Buffer Access with Incorrect Length Value

Affects Cisco IOS XE SoftwareSource CVE Database V5

0

Not known to be exploited · CVSS 8.6 High.

Data as of 26 Oct 2026, 09:15 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 24 Sep 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: 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 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Cisco Cisco IOS XE SoftwareAffected
  • =3.7.0
  • =3.7.1
  • =3.7.2
  • =3.7.3
  • =3.7.4
  • =3.7.5
  • =3.7.6
  • =3.7.7
  • =3.8.0
  • =3.8.1
  • =3.8.2
  • =3.9.1
  • =3.9.0
  • =3.9.2
  • =3.11.1
  • =3.11.2
  • =3.11.0
  • =3.11.3
  • =3.11.4
  • =3.12.0
  • =3.12.1
  • =3.12.2
  • =3.12.3
  • =3.12.4
  • =3.13.0
  • =3.13.1
  • =3.13.2
  • =3.13.3
  • =3.13.4
  • =3.13.5
  • =3.13.6
  • =3.13.7
  • =3.13.8
  • =3.13.9
  • =3.13.10
  • =3.14.0
  • =3.14.1
  • =3.14.2
  • =3.14.3
  • =3.14.4
  • =3.15.0
  • =3.15.1
  • =3.15.2
  • =3.15.3
  • =3.15.4
  • =3.16.0
  • =3.16.1
  • =3.16.2
  • =3.16.3
  • =3.16.4
  • =3.16.5
  • =3.16.6
  • =3.16.7
  • =3.16.8
  • =3.16.9
  • =3.16.10
  • =3.17.0
  • =3.17.1
  • =3.17.2
  • =3.17.3
  • =3.17.4
  • =16.1.1
  • =16.1.2
  • =16.1.3
  • =16.2.1
  • =16.2.2
  • =16.3.1
  • =16.3.2
  • =16.3.3
  • =16.3.4
  • =16.3.5
  • =16.3.6
  • =16.3.7
  • =16.3.8
  • =16.3.9
  • =16.3.10
  • =16.3.11
  • =16.4.1
  • =16.4.2
  • =16.4.3
  • =16.5.1
  • =16.5.2
  • =16.5.3
  • =3.18.0
  • =3.18.1
  • =3.18.2
  • =3.18.3
  • =3.18.4
  • =3.18.5
  • =3.18.6
  • =3.18.7
  • =3.18.9
  • =16.6.1
  • =16.6.2
  • =16.6.3
  • =16.6.4
  • =16.6.5
  • =16.6.6
  • =16.6.7
  • =16.6.8
  • =16.6.9
  • =16.6.10
  • =16.7.1
  • =16.7.2
  • =16.7.3
  • =16.7.4
  • =16.8.1
  • =16.8.2
  • =16.8.3
  • =16.9.1
  • =16.9.2
  • =16.9.3
  • =16.9.4
  • =16.9.5
  • =16.9.6
  • =16.9.7
  • =16.9.8
  • =16.10.1
  • =16.10.2
  • =16.10.3
  • =16.11.1
  • =16.11.2
  • =16.12.1
  • =16.12.2
  • =16.12.3
  • =16.12.8
  • =16.12.4
  • =16.12.5
  • =16.12.6
  • =16.12.7
  • =16.12.9
  • =16.12.10
  • =16.12.11
  • =16.12.12
  • =16.12.13
  • =17.1.1
  • =17.1.3
  • =17.2.1
  • =17.2.1v
  • =17.2.2
  • =17.2.3
  • =17.3.1
  • =17.3.2
  • =17.3.3
  • =17.3.4
  • =17.3.5
  • =17.3.6
  • =17.3.7
  • =17.3.8
  • =17.4.1
  • =17.4.2
  • =17.5.1
  • =17.6.1
  • =17.6.2
  • =17.6.3
  • =17.6.4
  • =17.6.5
  • =17.6.6
  • =17.6.7
  • =17.6.8
  • =17.7.1
  • =17.7.2
  • =17.10.1
  • =17.8.1
  • =17.9.1
  • =17.9.2
  • =17.9.3
  • =17.9.4
  • =17.9.5
  • =17.9.6
  • =17.11.1
  • =17.12.1
  • =17.12.2
  • =17.12.3
  • =17.12.4
  • =17.13.1
  • =17.14.1
  • =17.11.99
  • =17.15.1
  • =17.15.2
  • =17.16.1
Fixed in–

AI-suggested

European organizations should prioritize the following mitigation steps: 1) Immediate identification of all Cisco IOS XE devices running affected versions through asset inventory and network scanning. 3) Implement network-level filtering to block or restrict CAPWAP traffic from untrusted or external sources, limiting exposure to malformed packets. 4) Employ intrusion detection and prevention systems (IDS/IPS) with signatures or anomaly detection for malformed CAPWAP packets to detect and block exploitation attempts. 5) Segment network infrastructure to isolate critical Cisco devices from general user and internet traffic, reducing attack surface. 6) Regularly monitor device logs and network traffic for unusual reloads or CAPWAP anomalies that could indicate exploitation attempts. 7) Develop and test incident response plans specifically addressing potential DoS scenarios caused by device reloads. 8) Engage with Cisco support for guidance and early access to patches or workarounds. These measures go beyond generic advice by focusing on protocol-specific filtering, network segmentation, and proactive detection tailored to this vulnerability.

Description

A vulnerability in the Network-Based Application Recognition (NBAR) feature of Cisco IOS XE Software could allow an unauthenticated, remote attacker to cause an affected device to reload, causing a denial of service (DoS) condition. This vulnerability is due to improper handling of malformed Control and Provisioning of Wireless Access Points (CAPWAP) packets. An attacker could exploit this vulnerability by sending malformed CAPWAP packets through an affected device. A successful exploit could allow the attacker to cause the device to reload unexpectedly, resulting in a DoS condition.

References

Community reviews

Loading reviews…