Cisco Identity Services Engine Software vulnerability

A vulnerability in Cisco ISE and ISE-PIC could allow an authenticated, remote attacker to execute arbitrary commands on the underlying operating system of an affected device. To exploit this vulnerability, the attacker must have valid administrative credentials. This vulnerability is due to insufficient validation of user-supplied input. An attacker could exploit this vulnerability 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 deployments, successful exploitation of this vulnerability 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.

Published 17 Jun 2026Updated 25 Sep 20261 sources
CVSS 9.1

What happened

A vulnerability in Cisco ISE and ISE-PIC could allow an authenticated, remote attacker to execute arbitrary commands on the underlying operating system of an affected device. To exploit this vulnerability, the attacker must have valid administrative credentials. This vulnerability is due to insufficient validation of user-supplied input. An attacker could exploit this vulnerability 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 deployments, successful exploitation of this vulnerability 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.

Affected versions

Cisco Identity Services Engine Software: 3.1.0; 3.1.0 p1; 3.1.0 p3; 3.1.0 p2; 3.2.0; 3.1.0 p4; 3.1.0 p5; 3.2.0 p1; 3.1.0 p6; 3.2.0 p2; 3.1.0 p7; 3.3.0; 3.2.0 p3; 3.2.0 p4; 3.1.0 p8; 3.2.0 p5; 3.2.0 p6; 3.1.0 p9; 3.3 Patch 2; 3.3 Patch 1; 3.3 Patch 3; 3.4.0; 3.2.0 p7; 3.3 Patch 4; 3.4 Patch 1; 3.1.0 p10; 3.3 Patch 5; 3.3 Patch 6; 3.4 Patch 2; 3.3 Patch 7; 3.4 Patch 3; 3.5.0; 3.4 Patch 4; 3.3 Patch 8; 3.2 Patch 8; 3.5 Patch 1; 3.3 Patch 9; 3.2 Patch 9; 3.4 Patch 5; 3.5 Patch 3; 3.5 Patch 2; 3.3 Patch 10; 3.2 Patch 10; 3.1.0 p11 Fixed: See vendor advisory.

Why it matters

Review the vendor advisory and exposure of the affected product to determine operational impact.

Detection & mitigation

  • Apply vendor-provided updates or mitigations.
  • Review affected product exposure and access logs.

Public PoC references

No public PoC reference has passed the current publication threshold.