# CVE-2026-20013: Denial of service in Cisco Secure Firewall Adaptive Security Appliance (ASA) Software

> Unauthenticated remote attackers can cause denial of service on Cisco ASA and FTD devices by exhausting memory via crafted IKEv2 packets.

- **Severity:** Medium 5.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Mar 2026
- **Updated:** 4 Mar 2026
- **Also known as:** GHSA-mj8r-4vp9-fx97

## What is CVE-2026-20013?

CVE-2026-20013 is a medium-severity denial of service vulnerability in Cisco Adaptive Security Appliance Software, published on 4 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability in the IKEv2 feature of Cisco Secure Firewall ASA Software and Cisco Secure FTD Software could allow an unauthenticated, remote attacker to cause a DoS condition on an affected device that may also impact the availability of services to devices elsewhere in the network.

 This vulnerability is due to memory exhaustion caused by not freeing memory during IKEv2 packet processing. An attacker could exploit this vulnerability by sending crafted IKEv2 packets to an affected device. A successful exploit could allow the attacker to exhaust resources, causing a DoS condition that will eventually require the device to manually reload.

Weakness: CWE-401 (Missing Release of Memory after Effective Lifetime)

## Which versions are affected by CVE-2026-20013?

It affects 2 products.


Products: Cisco Adaptive Security Appliance Software, Cisco Secure Firewall Threat Defense.

## How do I fix CVE-2026-20013?

No fix has been published for CVE-2026-20013 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-20013 being exploited?

There is no known exploitation of CVE-2026-20013 in the wild and no public exploit code.

## Other vulnerabilities in Cisco Adaptive Security Appliance Software

- [CVE-2025-20333](https://insights.sbomify.com/CVE-2025-20333/): Cisco Secure Firewall Adaptive Security Appliance (ASA) and Secure Firewall Threat Defense (FTD) Buffer Overflow (critical 9.9, exploited in the wild)
- [CVE-2016-6366](https://insights.sbomify.com/CVE-2016-6366/): Cisco Adaptive Security Appliance (ASA) SNMP Buffer Overflow (high 8.8, exploited in the wild)
- [CVE-2026-20349](https://insights.sbomify.com/CVE-2026-20349/): Cisco Secure Firewall Adaptive Security Appliance (ASA) and Secure Firewall Threat Defense (FTD) Heap Inspection (high 8.6, exploited in the wild)
- [CVE-2024-20353](https://insights.sbomify.com/CVE-2024-20353/): Cisco ASA and FTD Denial of Service (high 8.6, exploited in the wild)
- [CVE-2016-6367](https://insights.sbomify.com/CVE-2016-6367/): Cisco Adaptive Security Appliance (ASA) CLI Remote Code Execution (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-20013 and fix it if it is affected.

What it is: CVE-2026-20013 is a medium-severity denial of service vulnerability in Cisco Adaptive Security Appliance Software, published on 4 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-20013 in the wild and no public exploit code.

Affected product: Cisco Adaptive Security Appliance Software. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-20013/ (Markdown: https://insights.sbomify.com/CVE-2026-20013/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-20013
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-20013
- OSV: https://osv.dev/vulnerability/CVE-2026-20013

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-20013/
Summaries are generated and may contain mistakes; the official description above is the record.