CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H
Called exploited the same day it was disclosed.
Measured from the CVE publication date to the earliest of 3 KEV catalogues that list it.
The life of this vulnerability
- CVE published
- First KEV listingsame day
- Last sighting10d
Gaps are compressed to equal steps. The elapsed time is printed under each.
Which catalogues call it exploited
- CISA KEVUS federallisted Aug 11, 2026
- EUVDENISA, European Unionlisted Aug 11, 2026
- VulnCheck KEVcommercial researchlisted Aug 11, 2026
- CIRCLaggregator, mirrors the abovelisted Aug 11, 2026, not counted
3 catalogues list it. CIRCL aggregates the others and is shown but not counted.
Public exploitation evidence
- reported exploitationcydome.io/maritime-cybersecurity-bulletin-august-21st-2026/
- reported exploitationeclypsium.com/blog/cve-2026-20349-someone-is-crashing-cisco-
- reported exploitationwww.hkcert.org/security-bulletin/cisco-products-multiple-vul
- reported exploitationprevidian.com/CVE-2026-20349
- reported exploitationsec.cloudapps.cisco.com/security/center/content/CiscoSecurit
- reported exploitationwww.cisa.gov/sites/default/files/feeds/known_exploited_vulne
6 public reports collected from VulnCheck and CIRCL, first on Aug 11, 2026. Each links to its original source. We have not verified them.
Description
A vulnerability in the Remote Access SSL VPN service for Cisco Secure Firewall Adaptive Security Appliance (ASA) Software and Cisco Secure Firewall Threat Defense (FTD) Software could allow an unauthenticated, remote attacker to cause the device to reload unexpectedly, resulting in a denial of service (DoS) condition. This vulnerability is due to insufficient error checking when processing HTTP requests. An attacker could exploit this vulnerability by sending a crafted HTTP request to the Remote Access SSL VPN service on an affected device. A successful exploit could allow the attacker to cause the affected device to reload, resulting in a DoS condition.
Required action (CISA)
Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.



