CVE-2024-20260: Cisco ASA and FTD SSL VPN denial-of-service scope expansion

Quick Answer

Cisco materially revised a High-rated advisory that includes CVE-2024-20260, affecting Cisco Secure Firewall ASA / FTD under the live advisory's conditions. Cisco does not separately state a CVE-specific Security Impact Rating (SIR); Common Vulnerability Scoring System (CVSS) base 8.6 (High). Confirm the exact platform, release, feature, and exposure; preserve relevant evidence; then follow Cisco's CVE-specific First Fixed guidance. Cisco reported no public announcement or malicious use for this CVE at the last check. That status and absence from CISA KEV are time-bounded and do not prove exploitation has never occurred.

Last verified: 2026-09-17 UTC from Cisco's advisory and CSAF record. Recheck both the affected-products and fixed-software sections before a production change.

Context

Status At A Glance

Product scope	Cisco Secure Firewall ASA / FTD
CVE	CVE-2024-20260
TechGeeks response tier	P1 — urgent
Publication	Material revision of an older advisory
First published	2024-10-23T16:00:00+00:00
Last updated	2026-09-16T16:05:50+00:00
Cisco advisory SIR	High
CVE-specific Cisco SIR	Not separately stated
CVSS base score / severity	8.6 — High
CVSS vector	CVSS v3.1 — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H
CISA KEV at last check	No — this is separate from Cisco severity and is not proof of no exploitation.
Cisco exploitation statement	The Cisco Product Security Incident Response Team (PSIRT) is not aware of any public announcements or malicious use of the vulnerability that is described in this advisory.

What Happened

Update for September 16, 2026: The original 1.0 version of this advisory was specific to the Cisco Adaptive Security Virtual Appliance (ASAv) and Cisco Secure Firewall Threat Defense Virtual (FTDv) models. However, it was later found that this vulnerability affects all Cisco Secure Firewall Adaptive Security Appliance (ASA) Software and Cisco Secure Firewall Threat Defense (FTD) Software platforms. A vulnerability in the VPN and management web servers of the Cisco Secure Firewall ASA Software and Cisco Secure FTD Software platforms could allow an unauthenticated, remote attacker to cause an affected device to run out of system memory or buffer blocks, which in turn could cause SSL VPN connection processing to slow down and eventually cease altogether. This vulnerability is due to a lack of proper memory management for new incoming SSL/TLS connections. An attacker could exploit this vulnerability by sending a large number of new incoming SSL/TLS connections to the targeted device. A successful exploit could allow the attacker to deplete system memory or buffers, resulting in a denial of service (DoS) condition. The memory or buffers could be reclaimed slowly if the attack traffic is stopped, but a manual reload may be required to restore operations quickly. Cisco has released software updates that address this vulnerability. There are no workarounds that address this vulnerability. This advisory is part of the October 2024 release of the Cisco ASA, FMC, and FTD Software Security Advisory Bundled Publication. For a complete list of the advisories and links to them, see Cisco Event Response: October 2024 Semiannual Cisco ASA, FMC, and FTD Software Security Advisory Bundled Publication.

Affected Scope

Treat all Cisco Secure Firewall ASA Software and Secure FTD Software platforms, hardware and virtual, as potentially affected when they run a vulnerable release and either SSL VPN or the management HTTP server is configured. Run show asp table socket | include SSL|DTLS; empty output means the device is not affected, while any output means it is affected. Secure FMC Software is not affected.

Match the exact hardware or virtual platform, installed train, patch level, enabled service, role, and management or data-plane exposure. A Cisco product-family name alone does not establish applicability.

Steps

What To Do Now

1. Confirm. Inventory Cisco Secure Firewall ASA / FTD and record platform, exact release, patch level, enabled feature, role, and exposure.
2. Preserve. Save UTC context plus off-device authentication, management, firewall, network, endpoint, and SIEM evidence before logs rotate or a disruptive change removes context.
3. Scope. Compare each asset with the live Cisco advisory, including configuration prerequisites and exclusions.
4. Reduce exposure. Cisco documents no workaround for this CVE. Use only supported exposure controls while preparing the permanent fix.
5. Remediate. Confirm the affected product, release, and configuration. Cisco provides no workaround; reduce exposure where operationally feasible. Enter the exact installed product, platform, and release in Cisco Software Checker and upgrade to the returned First Fixed release. The CVE-specific live advisory and Cisco Software Checker result control the First Fixed release; any combined hardening baseline is supplemental only.
6. Validate. Confirm the resulting version, service health, logging, expected access, an expected denial, failover or cluster state, and representative dependent workflows.
7. Escalate. If evidence or exposure creates concern, open incident response and Cisco TAC recovery work rather than treating patch completion as proof of trust.

Fixed Releases And Mitigation

Investigation And Recovery

Review management authentication, account and privilege changes, API and web requests, configuration changes, crashes or restarts, resource pressure, and relevant external network telemetry for the vulnerable period. Preserve original evidence and follow Cisco TAC or incident-response guidance for containment, credential rotation, trusted rebuild, or service restoration when findings warrant it.

Notes

Exploitation Evidence

Cisco's exact status at the last check: The Cisco Product Security Incident Response Team (PSIRT) is not aware of any public announcements or malicious use of the vulnerability that is described in this advisory.

This CVE was not present in the TechGeeks CISA KEV snapshot at the last check. Cisco's 'not aware' statement and absence from KEV are time-bounded evidence, not claims that exploitation is impossible or has never happened. Severity and exploitation status remain separate signals.

Validation And Boundaries

This notice is documentation-backed. TechGeeks did not reproduce the exploit or independently test every fixed build. It does not prove that all members of the product family are affected, that the activity is widespread, that a clean indicator search excludes compromise, or that an update restored trust. Cisco's live advisory controls affected and fixed release information.

Related TechGeeks Resources

• TechGeeks Security Notice Center
• All Security Notices
• What to Do When a Device Hits CISA KEV
• Router CVE Exposure, Version, and Mitigation Checklist
• IoT Firmware Update and End-of-Support Checklist
• Live Protect and Runtime Vulnerability Shielding

References

• Cisco security advisory
• Cisco CSAF record
• Cisco Security Advisory RSS feed
• NVD identifier record

Wrap-Up

Record whether CVE-2024-20260 applies. If it does, assign an owner and deadline appropriate to the High Cisco advisory SIR, preserve the evidence, complete Cisco's remediation, and document the validated result.

Correction policy: A material Cisco revision to scope, severity, exploitation status, workarounds, fixed software, or recovery guidance triggers an update and a new verification date.