Cisco Identity Services Engine Software vulnerability

A vulnerability in the SXP REST API of Cisco ISE could allow an authenticated, remote attacker to conduct SQL injection attacks. This vulnerability is due to insufficient validation of user-supplied input in REST API calls. An attacker could exploit this vulnerability by sending crafted input to an affected device. A successful exploit could allow the attacker to view or modify data on the underlying database for the affected device. In single-node deployments, successful exploitation of this vulnerability could cause the affected ISE node to become unavailable, resulting in a DoS condition. In that condition, endpoints that have not already authenticated would be unable to access the network until the node is restored. To exploit this vulnerability, the attacker must have valid administrative credentials, have the SXP service enabled, and have at least one SXP connection configured.

Published 16 Sep 2026Updated 18 Sep 20261 sources
CVSS 9.1

What happened

A vulnerability in the SXP REST API of Cisco ISE could allow an authenticated, remote attacker to conduct SQL injection attacks. This vulnerability is due to insufficient validation of user-supplied input in REST API calls. An attacker could exploit this vulnerability by sending crafted input to an affected device. A successful exploit could allow the attacker to view or modify data on the underlying database for the affected device. In single-node deployments, successful exploitation of this vulnerability could cause the affected ISE node to become unavailable, resulting in a DoS condition. In that condition, endpoints that have not already authenticated would be unable to access the network until the node is restored. To exploit this vulnerability, the attacker must have valid administrative credentials, have the SXP service enabled, and have at least one SXP connection configured.

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.3 Patch 11; 3.4 Patch 6; 3.2 Patch 10; 3.1.0 p72; 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.