⚠ Reference material — not professional advice. Test in staging, back up first, verify against your specific version. Use your own judgment for your environment.
● High · CVSS 8.6

How to Fix CVE-2026-20012: Denial of Service in IOS

Other vulnerabilities in the same area that are worth patching alongside this one:

*By Sai Kiran Pandrala*

⚡ At a glance
SeverityCVSS 8.6 - High
Actively exploited?Not currently listed in CISA KEV
Affected15.2(1)S, 15.2(2)S, 15.2(1)S1, 15.2(4)S, 15.2(1)S2, 15.2(2)S1, and others
Fixed inSee vendor advisory
Type (CWE)CWE-401: Missing Release of Memory after Effective Lifetime

What is CVE-2026-20012?

CVE-2026-20012 is a denial of service flaw in IOS. A crafted request triggers a code path that crashes or hangs the service, taking the product offline for legitimate users. Vendor description: A vulnerability in the Internet Key Exchange version 2 (IKEv2) feature of Cisco IOS Software, Cisco IOS XE Software, Cisco Secure Firewall Adaptive Security Appliance (ASA) Software, and Cisco 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 on an affected device. This vulnerability is due to improper parsing of IKEv2 packets.

Why this CVE matters

Denial-of-service flaws in a network gateway or firewall have an outsize operational impact. A single packet that reboots an inline device takes down everything behind it, which is why even non-RCE bugs on these products warrant priority patching.

For deployments of IOS that have been exposed to the public internet during the disclosure window, the operating assumption should be that scanning has already happened. Even where exploitation has not been publicly observed, scanning for the vulnerable fingerprint is cheap and routine. Patching closes the door; log review and credential rotation close out the rest of the response.

Am I affected?

You are affected if your installation matches any of these version ranges:

Check your installed version against the list above. If you cannot determine the version, treat the system as affected and follow the upgrade path below.

On Cisco IOS / IOS XE systems, run show version to read the running image and compare against the affected ranges. For ASA / FTD, use show version from privileged EXEC mode.

How to fix CVE-2026-20012

  1. Read the vendor advisory in full: https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-asa-ftd-ios-dos-kPEpQGGK
  2. Upgrade IOS to the patched build listed in the vendor advisory.
  3. Back up the configuration (and database, where applicable) before upgrading.
  4. Apply the patch in a maintenance window. For HA pairs, upgrade the standby node first, fail over, then upgrade the former primary.
  5. Restart the affected service so the patched binary loads, then verify the new version (see verification section).

Cisco device CLI


# Confirm the patched build against the vendor advisory: https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-asa-ftd-ios-dos-kPEpQGGK
# 1. Confirm the running image on the Cisco IOS device.
show version
show inventory

# 2. Stage the patched image from Cisco's Software Center, verify SHA512 before installing.
copy ftp://10.0.0.10/ios-<patched-version-from-advisory>.bin flash:

# 3. Set boot variable and reload during a maintenance window.
configure terminal
no boot system
boot system flash:ios-<patched-version-from-advisory>.bin
end
write memory
reload

# 4. After reboot, confirm the new image.
show version | include System image

Windows (PowerShell, run as administrator)


# Confirm the patched build against the vendor advisory: https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-asa-ftd-ios-dos-kPEpQGGK
# 1. Apply current Windows Updates - vendor patches ship as monthly rollups.
Install-Module -Name PSWindowsUpdate -Force -SkipPublisherCheck -Confirm:$false
Import-Module PSWindowsUpdate
Get-WindowsUpdate -AcceptAll -Install -AutoReboot

# 2. Verify the specific KB landed (replace KB number from the advisory).
Get-HotFix | Where-Object { $_.HotFixID -match 'KB' }

# 3. Confirm the running product version (target: the build named in the advisory).
Get-CimInstance Win32_Product | Where-Object { $_.Name -match 'IOS' } |
  Select-Object Name, Version

# Or for an MSU file from the Microsoft Update Catalog:
# wusa.exe C:\Patches\windows10.0-kb<id>-x64.msu /quiet /norestart
# shutdown /r /t 60

Verify the fix landed


# Confirm the patched build against the vendor advisory: https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-asa-ftd-ios-dos-kPEpQGGK
# 1. Confirm the running version equals the advisory's fixed-in build.
#    (Use the platform-specific version probe from the commands above.)

# 2. Re-scan with your vulnerability scanner (Nessus, Qualys, Tenable, OpenVAS).
#    The scanner should no longer flag CVE-2026-20012 on the patched target.

# 3. Inspect recent service and kernel logs for crash-loops or rollback events.
journalctl --since "10 minutes ago" | tail -200
dmesg --since "10 minutes ago" | tail -100

If you cannot patch immediately

Front the service with rate limiting and drop malformed packets at a load balancer or IPS. Patch to remove the underlying crash condition.

How to verify the fix worked

If your installation was internet-reachable during the disclosure window, treat log review as part of the remediation rather than an optional follow-up. Look for repeated service restarts, crash logs from the affected daemon, and core files generated around the time of any anomalous traffic. A memory-corruption flaw used for exploitation often leaves a trail of failed attempts before the successful one.

Frequently asked questions

Is CVE-2026-20012 being exploited in the wild?

Public exploitation has not been confirmed by CISA at the time of writing. Treat the patch as time-sensitive anyway; reports often lag actual abuse.

Will a WAF or IDS rule fully mitigate CVE-2026-20012?

No. Network-layer filters can reduce noise and slow opportunistic scanners, but they will not stop a determined attacker. The vendor patch is the only durable fix.

How long should I plan for the upgrade?

Typical vendor-documented upgrade windows for IOS run from a few minutes to under an hour depending on cluster size. Test in a staging environment first and follow the vendor's documented HA upgrade order.

References

*This guide was assembled from the official vendor advisory, the NVD record, and the CISA KEV catalog entry on 2026-05-25. Always confirm against the vendor advisory before applying changes in production.*