cisco-sa-ise-mult-vul-ymSsTLCcCriticalCVSS 9.1

Cisco Identity Services Engine Authenticated Remote Code Execution and API Vulnerabilities

Published
September 16, 2026
Last Modified
September 16, 2026

🔗 CVE IDs covered (3)

CVE-2026-20282 →CVE-2026-20283 →CVE-2026-20284 →

📋 Description

Multiple vulnerabilities in Cisco Identity Services Engine (ISE) could allow an authenticated, remote attacker to conduct SQL injections, modify data, or execute arbitrary commands on the underlying operating system on an affected device.

For more information about these vulnerabilities, see the Details ["#details"] section of this advisory.

Note: For CVE-2026-20282 and CVE-2026-20283, Cisco has assigned a Security Impact Rating (SIR) of High rather than Medium as the scores indicate. The reason is that it is easy to get to root from the achieved privilege level.

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

This advisory is part of a group of advisories. For a complete list of the advisories and links to them, see Cisco Advance Notification for Publication of September 16, 2026, Security Advisories ["https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-notice-jfxK98ZP"]. In addition, for further documentation of improvements and fixes in Cisco Identity Services Engine, see Cisco Identity Services Engine Security Hardening Release: September 2026 ["https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-hardening-ise-XU5EwX5T"].

CVE-2026-20282 — Cisco Identity Services Engine Authenticated Remote Code Execution (CVSS 3.1 4.9, CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N) CVE-2026-20283 — Cisco Identity Services Engine IPSec Open API Command Injection Vulnerability (CVSS 3.1 6.5, CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N) CVE-2026-20284 — Cisco Identity Services Engine REST API SQL Injection Vulnerability (CVSS 3.1 9.1, CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H)

🎯 Affected products49

  • Cisco Identity Services Engine Software
  • Cisco Identity Services Engine Software 3.1.0
  • Cisco Identity Services Engine Software 3.1.0 p1
  • Cisco Identity Services Engine Software 3.1.0 p10
  • Cisco Identity Services Engine Software 3.1.0 p11
  • Cisco Identity Services Engine Software 3.1.0 p12
  • Cisco Identity Services Engine Software 3.1.0 p2
  • Cisco Identity Services Engine Software 3.1.0 p3
  • Cisco Identity Services Engine Software 3.1.0 p4
  • Cisco Identity Services Engine Software 3.1.0 p5
  • Cisco Identity Services Engine Software 3.1.0 p6
  • Cisco Identity Services Engine Software 3.1.0 p7
  • Cisco Identity Services Engine Software 3.1.0 p8
  • Cisco Identity Services Engine Software 3.1.0 p9
  • Cisco Identity Services Engine Software 3.2 Patch 10
  • Cisco Identity Services Engine Software 3.2 Patch 11
  • Cisco Identity Services Engine Software 3.2 Patch 8
  • Cisco Identity Services Engine Software 3.2 Patch 9
  • Cisco Identity Services Engine Software 3.2.0
  • Cisco Identity Services Engine Software 3.2.0 p1
  • Cisco Identity Services Engine Software 3.2.0 p2
  • Cisco Identity Services Engine Software 3.2.0 p3
  • Cisco Identity Services Engine Software 3.2.0 p4
  • Cisco Identity Services Engine Software 3.2.0 p5
  • Cisco Identity Services Engine Software 3.2.0 p6
  • Cisco Identity Services Engine Software 3.2.0 p7
  • Cisco Identity Services Engine Software 3.3 Patch 1
  • Cisco Identity Services Engine Software 3.3 Patch 10
  • Cisco Identity Services Engine Software 3.3 Patch 11
  • Cisco Identity Services Engine Software 3.3 Patch 2
  • +19 more not shown

✅ Remediation

Cisco has released software updates that address this vulnerability. https://software.cisco.com Workaround: CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment. Workarounds: CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

🔗 References (8)