Cisco Identity Services Engine Incorrect Use of Privileged APIs
CVE-2026-76460 is a critical-severity incorrect use of privileged apis vulnerability in Cisco Identity Services Engine Software from Cisco, with a CVSS 3.1 base score of 10.0 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. Affected Cisco Identity Services Engine Software versions: 3.1.0 p8; 3.1.0 p9; 3.3 Patch 2, and others listed below. The record does not name a fixed version, so check the vendor advisory. CISA added it to the Known Exploited Vulnerabilities catalogue on September 16, 2026, which means attacks have been observed in the wild.
Attackers are already exploiting this vulnerability, according to CISA.
What to do
- Check which version of Cisco Identity Services Engine Software you run against the affected versions below, and install the vendor's latest release.
- CISA's required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.
- Read the advisory on sec.cloudapps.cisco.com for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Cisco | 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; and 22 more ranges | Not stated |
| Cisco | Cisco ISE Passive Identity Connector | 3.4.0; 3.5.0 | Not stated |
| Cisco | Identity Services Engine | 3.1.0; 3.2.0; 3.3.0; 3.4.0; 3.5.0 | Not stated |
| Cisco | Identity Services Engine Passive Identity Connector | 3.1.0; 3.2.0; 3.3.0; 3.4.0 | Not stated |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- ChangedThe attack can reach beyond the vulnerable component into other systems.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H. Scored by CNA (cisco.com).
Official description
A vulnerability in an API of Cisco Identity Services Engine (ISE) could allow an unauthenticated, remote attacker to bypass authentication. This vulnerability is due to insufficient authentication control on an API endpoint. An attacker could exploit this vulnerability by sending a crafted request to an affected API endpoint. A successful exploit could allow the attacker to gain unauthorized access to the affected device by bypassing the web-based management interface.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Incorrect Use of Privileged APIs
The product does not conform to the API requirements for a function call that requires extra privileges. This could allow attackers to gain privileges by causing the function to be called incorrectly.
How developers prevent this class of flaw
- Before calling privileged APIs, always ensure that the assumptions made by the privileged code hold true prior to making the call.
- Know architecture and implementation weaknesses of the privileged APIs and make sure to account for these weaknesses before calling the privileged APIs to ensure that they can be called safely.
- If privileged APIs make certain assumptions about data, context or state validity that are passed by the caller, the calling code must ensure that these assumptions have been validated prior to making the call.
More Incorrect Use of Privileged APIs vulnerabilities (CWE-648)
Timeline
- CVE record published.
- Added to CISA's Known Exploited Vulnerabilities catalogue.
- CISA published its SSVC assessment (exploitation: active, automatable: yes, technical impact: total).
- Deadline for US federal agencies to remediate, set by CISA.
- Record last changed materially (score, affected products, status or references).
References
Advisories
Third-party and government advisories
- cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-76460US Government Resource
Our coverage
Other vulnerabilities in Cisco Identity Services Engine Software
- 7.6 High severity
- 7.2 High severity
- 8.6 High severity
- 7.1 High severity
- 9.1 Critical severity
- 7.5 High severity
Recent Incorrect Use of Privileged APIs vulnerabilities
- 8.8 High severity
- 8.4 High severity
- 7.5 High severity
- 9.1 Critical severity
- 9.8 Critical severity
- 9.9 Critical severity
Spotted an error? Tell us.