SARA / Free Tools / KEV / CVE-2025-20362

CVE-2025-20362 on CISA KEV

Update: On November 5, 2025, Cisco became aware of a new attack variant against devices running Cisco Secure ASA Software or Cisco Secure FTD Software releases that are affected by CVE-2025-20333 and CVE-2025-20362. This attack can cause unpatched devices to unexpectedly reload,

CISA KEV — Actively Exploited

Update: On November 5, 2025, Cisco became aware of a new attack variant against devices running Cisco Secure ASA Softwar

Vendor / Product
— / Cisco / Secure Firewall Adaptive Security Appliance and Secure Firewall Threat Defense
Added to KEV
2025-09-25
BOD 22-01 due
Ransomware use
Unknown
CVSS / EPSS
8.6 HIGH · EPSS 85.54%

01What CISA says about this vulnerability

Update: On November 5, 2025, Cisco became aware of a new attack variant against devices running Cisco Secure ASA Software or Cisco Secure FTD Software releases that are affected by CVE-2025-20333 and CVE-2025-20362. This attack can cause unpatched devices to unexpectedly reload, leading to denial of service (DoS) conditions. Cisco strongly recommends that all customers upgrade to the fixed…

02Required action — verbatim from CISA

Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.

03Notes & references

04SARA's analyst layer — why this matters

This vulnerability is currently on the CISA KEV list, which CISA only adds CVEs to when there is reliable evidence of active exploitation in the wild. For federal civilian agencies, BOD 22-01 requires remediation by the due date above. For everyone else, KEV is the strongest "patch immediately" signal you can get from public threat intel.

05Affected products (summary)

No structured affected-product list available — see references below for vendor advisories.

06Detection

Open the Sigma generator with a pre-filled prompt for this CVE to draft a starting detection:

Open in Sigma generator →

Programmatic KEV data?
SARA's API returns KEV, CVSS, EPSS + analyst summary in one call.
Read the API reference →