Identity Services Engine

Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.

Lifecycle evidence status

This CVE identity is linked to the Lifecycle record Cisco Identity Services Engine. Use that record for publisher support phases and retirement dates.

A missing support date does not mean the product is supported. CVE publication dates and affected-version ranges must not be interpreted as EOL dates.

CVE-observed version history

CVE	Published	Affected versions	Fixed version information	Publisher evidence
CVE-2026-76460	16 Sep 2026	Cisco Identity Services Engine Software: 3.1.0 p8, 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 p11; Cisco ISE Passive Identity Connector: 3.4.0, 3.5.0	The Cyber Centre strongly recommends that organizations running Cisco ISE and ISE-PIC upgrade to the vendor-supported fixed software versions identified below. Affected product Affected releases Fixed releases Cisco Identity Services Engine (ISE) or ISE-PIC releases prior to 3.0 Migrate to a fixed release Cisco Identity Services Engine (ISE) or ISE-PIC release 3.1 3.1 Patch 12 Cisco Identity Services Engine (ISE) or ISE-PIC release 3.2 3.2 Patch 11 Cisco Identity Services Engine (ISE) or ISE-PIC release 3.3 3.3 Patch 12 Cisco Identity Services Engine (ISE) or ISE-PIC release 3.4 3.4 Patch 7 Cisco Identity Services Engine (ISE) or ISE-PIC release 3.5 3.5 Patch 4 The Cyber Centre also recommends organizations to: Apply vendor-provided security updates immediately. Cisco has released fixes for all three vulnerabilities. Prioritize remediation of CVE-2026-76460 due to confirmed in-the-wild exploitation. Review access logs for indicators of compromise (IoC), particularly suspicious usernames and unexpected API activity. Restrict access to management interfaces through access control lists (ACL), network segmentation, and trusted administration networks where feasible. If compromise is suspected, re-image affected nodes and restore from known-good backups, as attackers may obtain elevated privileges and remove evidence of exploitation. Monitor firewall, network, and authentication logs for anomalous activity associated with affected systems. Note: Organizations operating Common Criteria Footnote 10 evaluated configurations should review Cisco's advisory and apply the recommended updates in accordance with their change management and certification requirements. In addition, the Cyber Centre strongly recommends that organizations review and implement the Cyber Centre's Top 10 IT Security Actions Footnote 11 with an emphasis on the following topics: Consolidating, monitoring, and defending Internet gateways Patch operating systems and applications Harden operating systems and applications Isolate web-facing applications Should activity matching the content of this alert be discovered, recipients are encouraged to report via My Cyber Portal , or email contact@cyber.gc.ca .	Update reference ↗
CVE-2025-20337	16 Jul 2025	Cisco Identity Services Engine Software: 3.3.0, 3.3 Patch 2, 3.3 Patch 1, 3.3 Patch 3, 3.4.0, 3.3 Patch 4, 3.4 Patch 1, 3.3 Patch 5, 3.3 Patch 6; Cisco ISE Passive Identity Connector: 3.2.0, 3.1.0, 3.3.0, 3.4.0	No fixed version is explicitly recorded in the structured CVE data.	Update reference ↗
CVE-2025-20281	25 Jun 2025	Cisco Identity Services Engine Software: 3.3.0, 3.3 Patch 2, 3.3 Patch 1, 3.3 Patch 3, 3.4.0, 3.3 Patch 4, 3.4 Patch 1, 3.3 Patch 5, 3.3 Patch 6	No fixed version is explicitly recorded in the structured CVE data.	Update reference ↗

How this record is maintained

The CVE inventory is reconciled automatically from cve.blacktree.nl. Exact identity matches link to existing Lifecycle product or package histories. Unmatched products stay in a prioritised publisher-source research queue, and Lifecycle marks the date gap instead of inferring a support boundary from vulnerability data.