Widely deployed enterprise authentication infrastructure; authenticated RCE with root on Cisco ISE could cause broad network outages.
CVE-2026-20186
Authenticated RCE on Cisco ISE via crafted HTTP; root access possible.
Is CVE-2026-20186 being exploited?
Not confirmed. CVE-2026-20186 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 5.6% probability of exploitation in the next 30 days.
How severe is CVE-2026-20186?
CVE-2026-20186 is rated Critical with a CVSS score of 9.9. 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-20186?
Yes. A fix has been recorded for CVE-2026-20186. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-20186 affect?
CVE-2026-20186 affects Cisco Identity Services Engine (ISE). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-20186?
Patch ASAP when released; rotate credentials; restrict admin access; monitor ISE nodes.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Attacker with Read Only Admin creds can execute OS commands and escalate to root; DoS on a single ISE node could disrupt network access.
Immediate action required
- affected3.1.0
- affected3.1.0 p1
- affected3.1.0 p3
- affected3.1.0 p2
- affected3.2.0
- affected3.1.0 p4
- affected3.1.0 p5
- affected3.2.0 p1
- affected3.1.0 p6
- affected3.2.0 p2
- affected3.1.0 p7
- affected3.3.0
- affected3.2.0 p3
- affected3.2.0 p4
- affected3.1.0 p8
- affected3.2.0 p5
- affected3.2.0 p6
- affected3.1.0 p9
- affected3.3 Patch 2
- affected3.3 Patch 1
- affected3.3 Patch 3
- affected3.4.0
- affected3.2.0 p7
- affected3.3 Patch 4
- affected3.4 Patch 1
- affected3.1.0 p10
- affected3.3 Patch 5
- affected3.3 Patch 6
- affected3.4 Patch 2
- affected3.3 Patch 7
- affected3.4 Patch 3
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.