CrowdSec Warns of a New Wave of Exploitation of Critical CVE-2025-20281 Vulnerability in Cisco Identity Services Engine
CrowdSec has reported a surge in active exploitation of CVE-2025-20281, a critical remote code execution (RCE) vulnerability affecting Cisco’s Identity Services Engine (ISE), which carries a maximum CVSS score of 10.0. This opportunistic spike began on February 23, 2026, as attackers began to integrate this exploit into automated attack kits. For organizations that have yet to apply the necessary patches, the compromise of ISE could result in a total takeover of network access policies.
Cisco Identity Services Engine is a cornerstone of network security architecture within large enterprises and government agencies. It centralizes access policy enforcement for all devices connected to the network, determining which users and devices are allowed to access specific resources. A compromise of ISE effectively eliminates any network segmentation: an attacker with root access to ISE can create persistent backdoors, bypass access controls, and move laterally without restrictions across internal resources. The threat vector encompasses data theft as well as widespread ransomware deployment within the internal network. CVE-2025-20281 was disclosed on June 25, 2025, with a maximum severity rating of CVSS 10.0.
The vulnerability stems from insufficient validation of user-supplied data in Cisco’s ISE REST API. An unauthenticated remote attacker can send a forged HTTP request to the /ers/sdk endpoint, injecting arbitrary system commands into the JSON payload’s name field. This execution occurs with root privileges and does not require prior authentication or user interaction. The exploit’s profile—unauthenticated, no user interaction, remote—justifies the CVSS 10.0 rating, making it one of the most dangerous vulnerabilities in the enterprise network ecosystem. In response, CrowdSec released a detection rule on August 13, 2025, to identify and block exploitation attempts.
The lack of required authentication significantly broadens the attack surface: any ISE system with an exposed web interface or REST API is vulnerable to exploitation without needing any prior reconnaissance to gather credentials. Security Operations Center (SOC) teams should treat any request directed at /ers/sdk from IP addresses not listed within management networks as a potential compromise indication that must be prioritized for investigation.
Opportunistic Surge Detected Since February 23
CrowdSec’s cyber threat intelligence (CTI) data outlines two distinct phases of exploitation. Following the initial disclosure and the release of a proof-of-concept, attacks featured both targeted attempts—advanced persistent threats incorporating the exploit into specific campaigns—and opportunistic efforts. After stabilization, a new wave of attacks has been detected since February 23, 2026, largely driven by opportunistic actors who have integrated CVE-2025-20281 into their automated exploitation kits. This pattern is typical of the lifecycle of unpatched critical vulnerabilities: after the initial phase dominated by sophisticated actors, the democratization of the exploit via attack kits increases the number of potential attackers and the overall volume of attempts.
For Chief Information Security Officers (CISOs), this trend necessitates a re-evaluation of remediation priorities for organizations that may have delayed applying the Cisco patch. The inclusion of the exploit in automated kits means that the skill level required for exploitation is now minimal, and the volume of attempts is expected to increase independently of targeted campaigns.
Recommended Immediate Remediation Steps
Cisco has issued fixes in its official advisory, and immediate application of these patches is the only definitive remedy for the vulnerability. Additionally, CrowdSec recommends three operational actions. First, restrict access to ISE administrative interfaces and the REST API to trusted management networks and ensure there is no direct Internet exposure. Second, analyze access logs to identify any suspicious requests directed towards /ers/sdk, dating back at least to February 23, 2026. Third, deploy CrowdSec’s Web Application Firewall (WAF) to proactively block IP addresses listed in the Community Blocklist as sources exploiting this specific CVE.
For organizations subject to NIS 2 regulations, the compromise of a central component such as ISE falls within the scope of incidents that must be reported to the relevant authorities within designated timelines. Chief Information Officers (CIOs) and CISOs must ensure that incident management procedures explicitly cover this scenario, and that SOC teams have CrowdSec detection rules or equivalent measures activated on the relevant perimeters.



