Skip to main content
CVE-2025-20225VulnerabilityPublished

CVE-2025-20225: Cisco IOS · Memory Leak

Affects Cisco IOSSource CVE Database V5

0

Not known to be exploited · CVSS 5.8 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
5.8Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.7% chance of exploitation in 30 days – higher than 53% 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:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 14 Aug 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 2026-10-26.

What to do

AI-suggested

European organizations should prioritize the following mitigation steps: 1) Inventory and identify all Cisco IOS, IOS XE, ASA, and FTD devices running affected versions to assess exposure. 2) Monitor Cisco's official advisories and security bulletins for patches or updates addressing CVE-2025-20225 and apply them promptly once available. 3) Implement network-level protections such as access control lists (ACLs) or firewall rules to restrict incoming IKEv2 traffic to trusted IP addresses and networks, minimizing exposure to unauthenticated attackers. 4) Employ intrusion detection/prevention systems (IDS/IPS) with signatures or anomaly detection capable of identifying malformed or suspicious IKEv2 packets to block exploitation attempts. 5) Regularly monitor device memory usage and system logs for signs of memory leaks or instability that could indicate exploitation attempts. 6) Plan for rapid incident response procedures including device reboot protocols to restore service if a DoS condition occurs. 7) Consider deploying redundant VPN gateways and failover mechanisms to maintain connectivity during device reloads or outages. 8) Harden network segmentation to isolate VPN infrastructure from general internet-facing services, reducing attack surface. These targeted measures go beyond generic advice by focusing on controlling attack vectors specific to IKEv2 and maintaining operational resilience in the face of potential DoS attacks.

Description

A vulnerability in the Internet Key Exchange Version 2 (IKEv2) feature of Cisco IOS Software, IOS XE Software, Secure Firewall Adaptive Security Appliance (ASA) Software, and Secure Firewall Threat Defense (FTD) Software could allow an unauthenticated, remote attacker to trigger a memory leak, resulting in a denial of service (DoS) condition. This vulnerability is due to a lack of proper processing of IKEv2 packets. An attacker could exploit this vulnerability by sending crafted IKEv2 packets to an affected device. In the case of Cisco IOS and IOS XE Software, a successful exploit could allow the attacker to cause the device to reload unexpectedly. In the case of Cisco ASA and FTD Software, a successful exploit could allow the attacker to partially exhaust system memory, causing system instability such as being unable to establish new IKEv2 VPN sessions. A manual reboot of the device is required to recover from this condition.

References

Community reviews

Loading reviews…