Widely deployed Cisco Secure FMC; authenticated SQLi enabling full DB access and OS file reads could disrupt security management across enterprises.
CVE-2026-20002
Authenticated SQL injection in Cisco Secure FMC web UI.
Is CVE-2026-20002 being exploited?
Not confirmed. CVE-2026-20002 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.35% probability of exploitation in the next 30 days.
How severe is CVE-2026-20002?
CVE-2026-20002 is rated High with a CVSS score of 8.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-20002?
Yes. A fix has been recorded for CVE-2026-20002. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-20002 affect?
CVE-2026-20002 affects Cisco Secure Firewall Management Center (FMC), Cisco Secure FMC Software. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-20002?
Patch when available; restrict FMC access; rotate credentials.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Authenticated attacker can inject SQL via the web UI to read DB and OS files; remote via crafted requests with valid creds.
Patch when possible
- affected6.4.0
- affected6.4.0.1
- affected6.4.0.3
- affected6.4.0.2
- affected6.4.0.4
- affected6.4.0.5
- affected6.4.0.6
- affected6.4.0.7
- affected6.4.0.8
- affected6.4.0.9
- affected6.4.0.10
- affected6.4.0.11
- affected6.4.0.12
- affected6.4.0.13
- affected6.4.0.14
- affected6.4.0.15
- affected6.4.0.16
- affected6.4.0.17
- affected6.4.0.18
- affected7.0.0
- affected7.0.0.1
- affected7.0.1
- affected7.0.1.1
- affected7.0.2
- affected7.0.2.1
- affected7.0.3
- affected7.0.4
- affected7.0.5
- affected7.0.6
- affected7.0.6.1
- affected7.0.6.2
- affected7.0.6.3
- affected7.0.7
- affected7.0.8
- affected7.0.8.1
- affected7.1.0
- affected7.1.0.1
- affected7.1.0.2
- affected7.1.0.3
- affected7.2.0
- affected7.2.1
- affected7.2.2
- affected7.2.0.1
- affected7.2.3
- affected7.2.3.1
- affected7.2.4
- affected7.2.4.1
- affected7.2.5
- affected7.2.5.1
- affected7.2.6
- affected7.2.7
- affected7.2.5.2
- affected7.2.8
- affected7.2.8.1
- affected7.2.9
- affected7.2.10
- affected7.2.10.2
- affected7.2.10.1
- affected7.3.0
- affected7.3.1
- affected7.3.1.1
- affected7.3.1.2
- affected7.4.0
- affected7.4.1
- affected7.4.1.1
- affected7.4.2
- affected7.4.2.1
- affected7.4.2.2
- affected7.4.2.3
- affected7.4.2.4
- affected7.4.3
- affected7.6.0
- affected7.6.1
- affected7.6.2
- affected7.6.2.1
- affected7.6.3
- affected7.7.0
- affected7.7.10
- affected7.7.10.1
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.