Advisory

CVE-2026-76460: Critical Cisco ISE Authentication Bypass (CVSS 10.0) — Active Exploitation Confirmed

A CVSS 10.0 vulnerability in Cisco Identity Services Engine (ISE) and ISE Passive Identity Connector (ISE-PIC) allows an unauthenticated remote attacker to completely bypass authentication via a crafted API request, gaining unauthorized access to the management interface. This flaw is listed in the CISA Known Exploited Vulnerabilities catalog, confirming active exploitation in the wild.

TL;DR: Organizations running Cisco ISE or ISE-PIC must immediately apply vendor-supplied mitigations or patches and follow CISA BOD 26-04 guidance; if no mitigation is available, consider discontinuing use of the product until a fix is in place.

What Is the Vulnerability?

CVE-2026-76460 is a CVSS 3.1 score 10.0 (Critical) vulnerability affecting the API layer of Cisco Identity Services Engine (ISE) and Cisco ISE Passive Identity Connector (ISE-PIC). It is classified under CWE-648: Incorrect Use of Privileged APIs.

According to Cisco's advisory and the National Vulnerability Database (NVD), the root cause is insufficient authentication control on an API endpoint. An attacker who sends a specially crafted request to the vulnerable endpoint can bypass the web-based management interface entirely and gain unauthorized access to the affected device — with no credentials, no prior access, and no user interaction required.

The CVSS vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H tells the full story:

  • AV:N — exploitable over the network
  • AC:L — low attack complexity; no special conditions needed
  • PR:N — no privileges required
  • UI:N — no user interaction needed
  • S:C — scope changes, meaning impact extends beyond the vulnerable component itself
  • C:H / I:H / A:H — full compromise of confidentiality, integrity, and availability

Who and What Is Affected?

The affected products, as described by Cisco and CISA, are:

  • Cisco Identity Services Engine (ISE)
  • Cisco ISE Passive Identity Connector (ISE-PIC)

Cisco ISE is a widely deployed network access control (NAC) and policy enforcement platform used by enterprises and government agencies to authenticate users and devices, enforce security policies, and control network segmentation. ISE-PIC extends passive identity tracking capabilities to environments that do not require full ISE deployment.

Because ISE is frequently positioned as a trust broker for the entire network — handling authentication decisions for wired, wireless, and VPN access — a successful compromise of ISE can cascade into broad network access for an attacker.

The specific product versions affected are not enumerated in the verified facts provided here. Consult Cisco's official security advisory directly for the definitive list of affected releases and any version-specific guidance.

What Is the Impact?

The impact of a successful exploitation of CVE-2026-76460 is severe by every measure:

  • Complete authentication bypass: An unauthenticated remote attacker can gain access to the ISE management interface as if they were an authenticated administrator, without supplying any valid credentials.
  • Full triad compromise: The CVSS scoring reflects complete loss of confidentiality, integrity, and availability on the affected system.
  • Scope change: Because ISE acts as a central policy and authentication authority, unauthorized access to ISE can enable an attacker to modify network access policies, approve rogue devices, or observe identity and session data for users across the environment.
  • No barriers to exploitation: The low attack complexity, absence of privilege requirements, and lack of required user interaction mean this vulnerability is accessible to a wide range of threat actors.

CISA's Known Exploited Vulnerabilities (KEV) catalog listing — added 2026-09-16, the same day the CVE was published — indicates that this vulnerability has been actively exploited. Organizations should treat the threat as immediate rather than theoretical.

What Should You Do Right Now?

The required actions, as stated by CISA in the KEV catalog entry, are:

  1. Apply vendor mitigations immediately. Consult Cisco's official security advisory for patches and workarounds specific to your ISE and ISE-PIC version. Follow Cisco's instructions precisely.
  2. Comply with CISA BOD 26-04. CISA's Binding Operational Directive 26-04 establishes risk-based patching timelines for internet-facing assets. CISA has also issued specific Forensics Triage Requirements for this vulnerability — review the notes in the CISA KEV entry for the relevant URLs.
  3. Assess internet exposure. Determine whether your ISE or ISE-PIC management interfaces are reachable from the internet. CISA explicitly notes that stakeholders are responsible for evaluating each asset's internet exposure. If the management API is internet-accessible, treat this as an emergency-priority remediation.
  4. Restrict API endpoint access. Until a patch is applied, consider network-level controls (firewall rules, management VLANs, jump hosts) to limit which sources can reach ISE management interfaces.
  5. Conduct forensic triage. Given confirmed active exploitation, review logs and telemetry on ISE systems for indicators of unauthorized access. CISA has published Forensics Triage Requirements — follow those guidelines.
  6. Discontinue if no mitigation is available. CISA's required action explicitly states that if mitigations are unavailable and the product is a cloud service subject to BOD 26-04, organizations should discontinue use. Apply this judgment to your specific deployment context.

Primary references:

How External Testing Can Surface Exposure

Identifying exposure to CVE-2026-76460 before an attacker does requires understanding what an attacker sees from the outside. External, point-in-time security assessments can help in several ways:

  • Service discovery: An external scan can determine whether ISE management ports or API endpoints are reachable from the public internet, which dramatically increases risk for this vulnerability.
  • Version fingerprinting: Where banners or service responses permit, external assessments may identify the ISE version in use and flag it against affected version ranges published in Cisco's advisory.
  • Attack surface mapping: Even if the management interface is not directly internet-exposed, assessments can map which internal segments or DMZ hosts can reach ISE APIs — important for understanding lateral movement risk.
  • Validating access controls: Testing can verify whether network-level compensating controls (firewall ACLs, management-plane separation) are functioning as intended, independent of ISE's own authentication layer.

Because ISE is a trust anchor for network access decisions, understanding its exposure boundary is a foundational step. Point-in-time external assessments provide an attacker's-eye view without requiring any assumptions about internal configurations.

Sources & further reading: NVD CVE-2026-76460 and the CISA KEV catalog are the authority on affected and fixed versions. Vendor/independent analysis: sec.cloudapps.cisco.com, cisa.gov. This advisory contains no exploit code.

Frequently asked questions

Does an attacker need any credentials or existing access to exploit CVE-2026-76460?

No. The vulnerability can be exploited by an unauthenticated, remote attacker with no prior credentials and no user interaction required, as confirmed by both Cisco and the NVD description.

Is this vulnerability being actively exploited?

Yes. CISA added CVE-2026-76460 to the Known Exploited Vulnerabilities (KEV) catalog on 2026-09-16, which indicates confirmed active exploitation. CISA's KEV listing is the primary authoritative source for this determination.

Does this affect only the management interface, or the broader network?

The direct impact is unauthorized access to the ISE device via its web-based management interface. However, because Cisco ISE serves as a central network access control and policy enforcement platform, unauthorized administrative access to ISE can have cascading effects on the broader network — including the ability to manipulate access policies and authentication decisions for other users and devices.

What if a mitigation is not yet available for my version?

CISA's required action states that organizations should follow BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. For on-premises deployments, strong network-level isolation of ISE management interfaces should be treated as an urgent compensating control while awaiting a vendor patch. Consult Cisco's official security advisory for the most current guidance.