Cisco has released security patches for its Identity Services Engine (ISE) and ISE Passive Identity Connector (ISE-PIC), addressing two significant vulnerabilities. The most severe flaw, CVE-2026-20181, is a critical remote command execution (RCE) vulnerability with a CVSS score of 9.1. It allows an authenticated administrator to execute arbitrary commands with root privileges by sending a crafted HTTP request. The second flaw, CVE-2026-20190, is a high-severity information disclosure vulnerability (CVSS 7.5) that could allow an unauthenticated attacker to access sensitive data, including hashed credentials. Cisco has released patches and strongly advises customers to update their deployments immediately, as no workarounds are available.
Expert Insight: The combination of these two vulnerabilities presents a potential attack chain. An attacker could first exploit CVE-2026-20190 to steal hashed credentials, then crack them offline to gain administrative access, and finally use those credentials to achieve remote code execution via CVE-2026-20181.
The vulnerabilities affect the following Cisco products:
Patches are available for the following versions:
3.3 Patch 113.4 Patch 6The Cisco Product Security Incident Response Team (PSIRT) has stated that it is not aware of any public announcements or malicious use of these vulnerabilities. However, given the criticality of CVE-2026-20181, security teams should assume that exploitation will be attempted by threat actors now that the details are public.
Compromise of a Cisco ISE appliance can have a devastating impact on an organization's security posture. As a central network access control (NAC) solution, ISE governs which users and devices can access network resources. An attacker with root control over ISE could:
The following patterns may help identify vulnerable or compromised systems:
ISE Admin Access Logsise-tacacs-runtime/bin/bash), which would be a strong indicator of RCE.Cisco has confirmed there are no workarounds for these vulnerabilities. Patching is the only solution.
Applying the security patches provided by Cisco is the only way to fully remediate these vulnerabilities.
Mapped D3FEND Techniques:
Restrict network access to the ISE management interface to a limited set of trusted IPs as a compensating control.
Mapped D3FEND Techniques:
Ensure that administrative credentials for ISE are strong, unique, and rotated regularly. Limit the number of administrative accounts.
The primary and most urgent countermeasure is to apply the security patches released by Cisco for all affected Identity Services Engine (ISE) and ISE-PIC deployments. Given the 9.1 CVSS score of CVE-2026-20181 and the lack of workarounds, patching should be considered an emergency change. Security teams must identify all ISE nodes in their environment, determine their current software version, and deploy the appropriate patch (3.3P11, 3.4P6, or the 3.5 hotfix) according to a risk-based schedule, prioritizing internet-facing or otherwise exposed nodes. This action directly closes the command injection and information disclosure vulnerabilities, eliminating the threat.
As a critical compensating control, organizations must strictly enforce network access controls for the Cisco ISE management interface (TCP/8443). This interface should never be exposed to the public internet. Implement firewall rules or access control lists (ACLs) to ensure that only dedicated management workstations or specific IP addresses within a secure management VLAN can connect to the ISE admin GUI. This measure significantly reduces the attack surface for both CVE-2026-20181 (by limiting who can attempt to authenticate) and CVE-2026-20190 (by blocking unauthenticated remote attackers). This network isolation is a fundamental best practice for managing any critical security appliance.
To detect potential abuse of compromised credentials, configure authentication monitoring for the ISE platform. Forward ISE authentication logs to a SIEM and create rules to alert on anomalous administrative login events. This includes logins from geographically impossible locations (impossible travel), multiple failed logins followed by a success from a new IP, or any administrative login from an IP outside of the defined trusted management range. This provides a crucial detection layer for identifying when an attacker might be attempting to use credentials stolen via CVE-2026-20190 or other means to gain the access needed to exploit the RCE flaw.
Cisco publishes the security advisory for CVE-2026-20181 and CVE-2026-20190 and releases patches.

Cybersecurity professional with over 10 years of specialized experience in security operations, threat intelligence, incident response, and security automation. Expertise spans SOAR/XSOAR orchestration, threat intelligence platforms, SIEM/UEBA analytics, and building cyber fusion centers. Background includes technical enablement, solution architecture for enterprise and government clients, and implementing security automation workflows across IR, TIP, and SOC use cases.
Help others stay informed about cybersecurity threats
Every tactic, technique, and sub-technique used in this threat has been identified and mapped to the MITRE ATT&CK framework for consistent, actionable threat language.
Observables and indicators of compromise (IOCs) have been extracted and cataloged. Risk has been assessed and correlated with known threat actors and historical campaigns.
Detection rules, incident response steps, and D3FEND-aligned mitigation strategies are included so your team can act on this intelligence immediately.
Structured threat data is packaged as a STIX 2.1 bundle and can be visualized as an interactive graph — relationships between actors, malware, techniques, and indicators.
Sigma detection rules are derived from the threat techniques in this article and can be converted for deployment across any major SIEM or EDR platform.