CVE-2026-20147
Cisco Identity Services Engine command injection
- Published15 Apr 2026
Description
A vulnerability in Cisco ISE and Cisco 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 ISE 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.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:HAffected products
Remediation
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2026-20147 being actively exploited?
CVE-2026-20147 is not in the CISA KEV catalog. Its EPSS exploit probability is 10.4%.
How severe is CVE-2026-20147?
CVE-2026-20147 has a CVSS 3.1 base score of 9.9, rated critical. EPSS estimates a 10.4% probability of exploitation.
Which products are affected by CVE-2026-20147?
Affected products include Cisco Identity Services Engine, Cisco Identity Services Engine Passive Identity Connector.
How do I fix CVE-2026-20147?
Upgrade affected software to a fixed version, for example Cisco Identity Services Engine 3.1.0, Cisco Identity Services Engine Passive Identity Connector 3.1.0 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2026-20147 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.