Skip to main content
CVE-2025-20239VulnerabilityPublished

CVE-2025-20239: Cisco IOS · Memory Leak

Affects Cisco IOSSource CVE Database V5

0

Not known to be exploited · CVSS 8.6 High.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
8.6High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 49% 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 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

1. Immediate deployment of Cisco's security patches or updates for all affected IOS, IOS XE, ASA, and FTD versions once available is critical. Organizations should prioritize patching devices exposed to untrusted networks. 2. Implement network-level filtering to restrict inbound IKEv2 traffic to trusted sources only, minimizing exposure to crafted packets from unauthorized attackers. 3. Monitor network traffic for unusual or malformed IKEv2 packets that could indicate exploitation attempts. 4. Employ rate limiting on VPN gateways to reduce the impact of potential memory exhaustion attacks. 5. Maintain up-to-date backups and have incident response plans ready for rapid recovery including manual reboot procedures. 6. Consider deploying redundant VPN gateways or failover mechanisms to maintain connectivity during an attack or device reboot. 7. Conduct thorough inventory and version audits of Cisco devices to identify vulnerable systems and prioritize remediation. 8. Use Cisco’s recommended configuration best practices for IKEv2 and VPN services to reduce attack surface. 9. Engage with Cisco support and security advisories regularly to stay informed about patches and mitigation updates. These steps go beyond generic advice by emphasizing network filtering, monitoring, redundancy, and operational readiness specific to this vulnerability’s characteristics.

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…