CVE-2026-20349 is an insufficient-error-checking flaw in the Remote Access SSL VPN service of Cisco Secure Firewall ASA and FTD Software that lets a remote, unauthenticated attacker send a single crafted HTTP request and force the device to reload, causing a denial-of-service condition; Cisco's PSIRT became aware of active exploitation in August 2026, and there is no workaround short of upgrading.
Vulnerability summary
CVSS base score
8.6
High severity
EPSS score (FIRST)
1.0%
Probability of exploitation in the wild in the next 30 days
CISA KEV catalog
Yes
Listed as known exploited
Published
Vulnerability ID: CVE-2026-20349 · Source: NVD (Cisco PSIRT Secondary score only, not NVD Primary)
Affected components
| Component | CPE | Version range |
|---|---|---|
| Cisco Secure Firewall ASA Software | cpe:2.3:o:cisco:adaptive_security_appliance_software:*:*:*:*:*:*:*:* | 9.16.x through 9.24.x with Remote Access SSL VPN, IKEv2 Remote Access VPN with client services, or Zero Trust Network Access enabled; representative fixed releases include 9.16.4.103 and 9.22.3.26, per Cisco's per-train fixed-release table |
| Cisco Secure Firewall Threat Defense (FTD) Software | cpe:2.3:o:cisco:secure_firewall_threat_defense:*:*:*:*:*:*:*:* | 7.0.x through 10.1.x with the same VPN services enabled; representative fixed releases include 7.6.6 and 10.1.0, per Cisco's per-train fixed-release table |
What does this mean for affected devices?
CVE-2026-20349 is a heap-inspection / insufficient-error-checking vulnerability (CWE-244) in the Remote Access SSL VPN service of Cisco Secure Firewall Adaptive Security Appliance (ASA) Software and Secure Firewall Threat Defense (FTD) Software. NVD's description states the flaw "is due to insufficient error checking when processing HTTP requests," and that "an attacker could exploit this vulnerability by sending a crafted HTTP request to the Remote Access SSL VPN service on an affected device," causing the device to reload and resulting in a denial-of-service condition (NVD).
The CVE is rated by Cisco PSIRT (a CNA) at CVSS v3.1 8.6 (high), vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H — network-reachable, low attack complexity, no privileges or user interaction required, scope-changed, availability impact only. NVD's own vulnStatus for this record is "Analyzed," but NVD has not published an independent Primary CVSS metric of its own, so the 8.6 figure is Cisco's Secondary score, not NVD-confirmed (NVD).
Cisco's own advisory (cisco-sa-asaftd-vpn-dos-dzv4mQFF) confirms the vulnerability affects ASA Software releases 9.16 through 9.24 and FTD Software releases 7.0 through 10.1, but only on devices with Remote Access SSL VPN, IKEv2 Remote Access VPN with client services, or Zero Trust Network Access configured and enabled. Exploitation requires no authentication: an unauthenticated remote attacker sends a crafted HTTP request to the exposed service. The advisory lists per-train fixed releases — including ASA 9.16.4.103 and 9.22.3.26, and FTD 7.6.6 and 10.1.0, among others for each affected train — and states there is no workaround; Cisco PSIRT became aware of active exploitation of this vulnerability in August 2026 (Cisco Security Advisory cisco-sa-asaftd-vpn-dos-dzv4mQFF).
CISA added CVE-2026-20349 to the Known Exploited Vulnerabilities (KEV) catalog on 2026-08-11, with a required-action due date of 2026-08-14 under Binding Operational Directive 26-04, and lists known ransomware campaign use as "Unknown" (CISA KEV).
As of 2026-10-29, FIRST scores the probability of exploitation at 0.0101 (63.07th percentile) — modest for a confirmed KEV entry, consistent with a denial-of-service rather than code-execution primitive, though still worth prioritizing given the lack of a workaround (FIRST EPSS).
Any ASA or FTD device with SSL VPN, IKEv2 Remote Access VPN with client services, or ZTNA enabled should be upgraded to a fixed release from Cisco's per-train table immediately; because there is no workaround, exposure cannot otherwise be eliminated short of disabling the affected services.
Evidence
- Insufficient error checking when processing HTTP requests to the Remote Access SSL VPN service lets an unauthenticated remote attacker crash the device via a crafted HTTP request. — NVD
- CVSS v3.1 score is 8.6 (high), vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H, submitted by Cisco PSIRT as a Secondary score; NVD has not published its own Primary metric. — NVD
- Affects ASA 9.16-9.24 and FTD 7.0-10.1 with Remote Access SSL VPN, IKEv2 RA VPN with client services, or ZTNA enabled; no workaround; representative fixed releases ASA 9.16.4.103/9.22.3.26, FTD 7.6.6/10.1.0; Cisco PSIRT became aware of active exploitation in August 2026. — Cisco Security Advisory cisco-sa-asaftd-vpn-dos-dzv4mQFF
- Added to the CISA Known Exploited Vulnerabilities catalog on 2026-08-11, due date 2026-08-14, known ransomware campaign use listed as Unknown. — CISA KEV
- EPSS score is 0.0101 (63.07th percentile) as of 2026-10-29. — FIRST EPSS

Related advisories
Sources
Frequently asked questions
Is every Cisco ASA/FTD device vulnerable to CVE-2026-20349?
No. Only devices with Remote Access SSL VPN, IKEv2 Remote Access VPN with client services, or Zero Trust Network Access configured and enabled are affected; devices without those services active are not exposed (per Cisco Security Advisory cisco-sa-asaftd-vpn-dos-dzv4mQFF).
What's the actual impact of a successful attack?
A single crafted HTTP request to the Remote Access SSL VPN service forces the device to reload, causing a denial-of-service condition — not code execution or data theft (per NVD).
Why is the EPSS score relatively low despite the KEV listing?
FIRST's score of 0.0101 (63.07th percentile) as of 2026-10-29 is modest for a KEV entry; this page attributes that to the bug being a denial-of-service primitive rather than one that yields code execution or data access, though it's still worth prioritizing given the lack of a workaround (per FIRST EPSS).
Is the 8.6 CVSS figure an NVD-confirmed Primary rating?
No. NVD's vulnStatus is Analyzed, but the 8.6 score is Cisco PSIRT's own Secondary submission; NVD has not published an independent Primary metric (per NVD).
Can administrators mitigate this without upgrading?
No. Cisco's advisory states there is no workaround; exposure can only be eliminated by upgrading to a fixed release or disabling the affected VPN/ZTNA services entirely (per Cisco Security Advisory cisco-sa-asaftd-vpn-dos-dzv4mQFF).
Questions about this page?