Skip to content
VulniPulse
Critical9.9Cisco

Critical [CVE-2026-20180 +1] Cisco Identity Services Engine Remote Code Execution Vulnerabilities

This critical-severity Cisco advisory covers CVE-2026-20180 and CVE-2026-20186 affecting ISE, Identity Services Engine Software.

cisco-sa-ise-rce-4fverepv Published Apr 15, 2026Updated by vendor Apr 15, 2026
Affected products & platforms
CiscoISEIdentity Services Engine
Open vendor advisory

Android app · Google Play

Monitor future Cisco CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery

Summary

Multiple vulnerabilities in Cisco Identity Services Engine (ISE) could allow an authenticated, remote attacker to execute arbitrary commands on the underlying operating system of an affected device. To exploit these vulnerabilities, the attacker must have at least Read Only Admin credentials.

These vulnerabilities are due to insufficient validation of user-supplied input. An attacker could exploit these vulnerabilities by sending a crafted HTTP request to an affected device.

A successful exploit could allow the attacker to obtain user-level access to the underlying operating system and then elevate privileges to root. In single-node Cisco ISE deployments, successful exploitation of these vulnerabilities could cause the affected ISE node to become unavailable, resulting in a denial of service (DoS) condition.

In that condition, endpoints that have not already authenticated would be unable to access the network until the node is restored.

Cisco has released software updates that address these vulnerabilities. There are no workarounds that address these vulnerabilities.

Affected products named by the advisory: Identity Services Engine Software.

Affected versions
  • Scope: These vulnerabilities affect Cisco ISE, regardless of device configuration.
  • Earlier than 3.2 — Migrate to a fixed release
  • Release 3.2 (first fixed: 3.2 Patch 8)
  • Release 3.3 (first fixed: 3.3 Patch 8)
  • Release 3.4 (first fixed: 3.4 Patch 4)

Official advisory · high-confidence parse· fetched 2 months ago·verify at source

Fixed versions
  • 3.2 Patch 8
  • 3.3 Patch 8
  • 3.4 Patch 4

Official advisory · high-confidence parse· fetched 2 months ago·verify at source

Mitigation checklist

Recommended fix / mitigation
  • Upgrade to the first fixed release for your train per the Fixed Releases table in this advisory.
  • Earlier than 3.2: migrate to a fixed release.
  • Release 3.2: upgrade to 3.2 Patch 8.
  • Release 3.3: upgrade to 3.3 Patch 8.
  • Release 3.4: upgrade to 3.4 Patch 4.
Workaround status
  • There are no workarounds that address these vulnerabilities.

Official advisory · high-confidence parse· fetched 2 months ago·verify at source

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.