Cisco Firepower Threat Defense vulnerabilities: known CVEs & security history
Cisco · Network security · 222 tracked CVEs · 10 actively exploited · updated June 2026 · what is a CVE? →
This is the full list of known vulnerabilities (CVEs) across all Cisco Firepower Threat Defense release lines — 222 in total, with 10 actively exploited in the wild. A CVE here doesn't mean your version is affected — check Cisco Firepower Threat Defense's current status and the safe version to run.
Known Cisco Firepower Threat Defense CVEs
Actively-exploited and most-severe first. Showing the top 80 of 222. Open any CVE for full details.
| CVE | Severity | CVSS | EPSS | Year |
|---|---|---|---|---|
| CVE-2021-44228⚡ exploited | critical | 10 | 100% | 2021 |
| CVE-2025-20333⚡ exploited | critical | 9.9 | 29% | 2025 |
| CVE-2024-20353⚡ exploited | high | 8.6 | 63% | 2024 |
| CVE-2023-44487⚡ exploited | high | 7.5 | 100% | 2023 |
| CVE-2020-3452⚡ exploited | high | 7.5 | 100% | 2020 |
| CVE-2020-3259⚡ exploited | high | 7.5 | 72% | 2020 |
| CVE-2018-0296⚡ exploited | high | 7.5 | 100% | 2018 |
| CVE-2025-20362⚡ exploited | medium | 6.5 | 84% | 2025 |
| CVE-2024-20359⚡ exploited | medium | 6 | 17% | 2024 |
| CVE-2023-20269⚡ exploited | medium | 5 | 22% | 2023 |
| CVE-2018-0101 | critical | 10 | 87% | 2018 |
| CVE-2024-20412 | critical | 9.3 | 0% | 2024 |
| CVE-2020-3187 | critical | 9.1 | 97% | 2020 |
| CVE-2025-20363 | critical | 9 | 8% | 2025 |
| CVE-2022-20759 | high | 8.8 | 28% | 2022 |
| CVE-2019-12675 | high | 8.8 | 0% | 2019 |
| CVE-2025-20182 | high | 8.6 | 0% | 2025 |
| CVE-2024-20495 | high | 8.6 | 1% | 2024 |
| CVE-2024-20494 | high | 8.6 | 1% | 2024 |
| CVE-2024-20402 | high | 8.6 | 1% | 2024 |
| CVE-2024-20330 | high | 8.6 | 1% | 2024 |
| CVE-2023-20095 | high | 8.6 | 1% | 2023 |
| CVE-2023-20083 | high | 8.6 | 1% | 2023 |
| CVE-2023-20244 | high | 8.6 | 1% | 2023 |
| CVE-2023-20086 | high | 8.6 | 1% | 2023 |
| CVE-2023-20006 | high | 8.6 | 1% | 2023 |
| CVE-2022-20947 | high | 8.6 | 1% | 2022 |
| CVE-2022-20946 | high | 8.6 | 1% | 2022 |
| CVE-2022-20767 | high | 8.6 | 2% | 2022 |
| CVE-2022-20760 | high | 8.6 | 1% | 2022 |
| CVE-2022-20757 | high | 8.6 | 1% | 2022 |
| CVE-2022-20751 | high | 8.6 | 1% | 2022 |
| CVE-2022-20746 | high | 8.6 | 1% | 2022 |
| CVE-2022-20745 | high | 8.6 | 1% | 2022 |
| CVE-2022-20715 | high | 8.6 | 1% | 2022 |
| CVE-2021-34704 | high | 8.6 | 1% | 2022 |
| CVE-2021-1573 | high | 8.6 | 1% | 2022 |
| CVE-2021-40118 | high | 8.6 | 1% | 2021 |
| CVE-2021-40117 | high | 8.6 | 1% | 2021 |
| CVE-2021-40116 | high | 8.6 | 1% | 2021 |
| CVE-2021-34793 | high | 8.6 | 1% | 2021 |
| CVE-2021-34792 | high | 8.6 | 1% | 2021 |
| CVE-2021-34783 | high | 8.6 | 2% | 2021 |
| CVE-2021-34781 | high | 8.6 | 1% | 2021 |
| CVE-2021-1504 | high | 8.6 | 2% | 2021 |
| CVE-2021-1501 | high | 8.6 | 1% | 2021 |
| CVE-2021-1445 | high | 8.6 | 2% | 2021 |
| CVE-2021-1402 | high | 8.6 | 1% | 2021 |
| CVE-2020-3572 | high | 8.6 | 2% | 2020 |
| CVE-2020-3571 | high | 8.6 | 1% | 2020 |
| CVE-2020-3563 | high | 8.6 | 1% | 2020 |
| CVE-2020-3562 | high | 8.6 | 2% | 2020 |
| CVE-2020-3533 | high | 8.6 | 2% | 2020 |
| CVE-2020-3529 | high | 8.6 | 2% | 2020 |
| CVE-2020-3528 | high | 8.6 | 1% | 2020 |
| CVE-2020-3436 | high | 8.6 | 2% | 2020 |
| CVE-2020-3373 | high | 8.6 | 2% | 2020 |
| CVE-2020-3304 | high | 8.6 | 4% | 2020 |
| CVE-2020-3283 | high | 8.6 | 2% | 2020 |
| CVE-2020-3196 | high | 8.6 | 2% | 2020 |
| CVE-2020-3191 | high | 8.6 | 2% | 2020 |
| CVE-2020-3189 | high | 8.6 | 2% | 2020 |
| CVE-2019-15256 | high | 8.6 | 2% | 2019 |
| CVE-2019-1714 | high | 8.6 | 2% | 2019 |
| CVE-2019-1708 | high | 8.6 | 2% | 2019 |
| CVE-2019-1703 | high | 8.6 | 3% | 2019 |
| CVE-2019-1694 | high | 8.6 | 3% | 2019 |
| CVE-2018-15462 | high | 8.6 | 2% | 2019 |
| CVE-2018-15388 | high | 8.6 | 2% | 2019 |
| CVE-2019-1669 | high | 8.6 | 1% | 2019 |
| CVE-2018-15454 | high | 8.6 | 4% | 2018 |
| CVE-2018-0240 | high | 8.6 | 4% | 2018 |
| CVE-2018-0231 | high | 8.6 | 5% | 2018 |
| CVE-2018-0230 | high | 8.6 | 2% | 2018 |
| CVE-2018-0228 | high | 8.6 | 4% | 2018 |
| CVE-2021-1493 | high | 8.5 | 1% | 2021 |
| CVE-2023-20063 | high | 8.2 | 0% | 2023 |
| CVE-2020-3514 | high | 8.2 | 0% | 2020 |
| CVE-2019-12674 | high | 8.2 | 0% | 2019 |
| CVE-2018-0453 | high | 8.2 | 0% | 2018 |
142 older / lower-severity CVEs not shown — see Cisco Firepower Threat Defense's full record.
Is my Cisco Firepower Threat Defense version affected?
The list above spans every release. To know whether your version is affected — and the minimum safe version to upgrade to — check it directly.
Check your Cisco Firepower Threat Defense version → · Monitor Cisco Firepower Threat Defense for new CVEs →
Cisco Firepower Threat Defense vulnerabilities — frequently asked
How many known vulnerabilities does Cisco Firepower Threat Defense have?
IsItPatched tracks 222 CVEs for Cisco Firepower Threat Defense, 10 of which are actively exploited (CISA KEV). 6 are critical-severity and 114 high-severity. These span every release line — what matters is whether the version you run is affected.
Does Cisco Firepower Threat Defense have any actively-exploited vulnerabilities?
Yes — 10 Cisco Firepower Threat Defense CVEs are in CISA's Known Exploited Vulnerabilities catalog, meaning they are confirmed exploited in the wild (3 linked to ransomware). Patch these as a priority.
What is the most severe Cisco Firepower Threat Defense vulnerability?
Among tracked issues, CVE-2021-44228 (CRITICAL, CVSS 10), which is actively exploited, ranks highest — a Improper input validation weakness.
Is Cisco Firepower Threat Defense safe to use?
It depends on the version. The latest supported Cisco Firepower Threat Defense release clears the known issues; older versions may still be affected. Check the exact version you run for a verdict.
CVE data aggregated from NVD, CISA KEV and EPSS (FIRST.org). Related: Cisco Firepower Threat Defense security status · Cisco Firepower Threat Defense end-of-life · actively-exploited CVEs. Always verify against Cisco's advisories — see our disclaimer.