Skip to content
Server Security Center
KEVcritical10.0

CVE-2026-76460: Cisco Identity Services Engine Incorrect Use of Privileged APIs

Cisco Identity Services Engine · listed in the CISA catalog of actively exploited vulnerabilities since 2026-09-16.

CVSS v3.1 (CVE record)
10.0
critical
EPSS (exploit probability, 30 days)
76%
higher than 99.5% of all CVEs
Added to CISA KEV
2026-09-16
US federal due date 2026-09-19
Automatable (CISA SSVC)
yes
technical impact: total

CVE-2026-76460 explained

CVE-2026-76460 is a critical authentication bypass in an API of Cisco Identity Services Engine (ISE) and Cisco ISE Passive Identity Connector. Insufficient authentication control on an API endpoint lets an unauthenticated remote attacker gain unauthorized access to the device. CISA lists it as known to be exploited.

Impact

An unauthenticated attacker with network access can bypass the web-based management interface and gain unauthorized access to the affected device. No user interaction is needed, and attack complexity is low. Confidentiality, integrity and availability impacts are high, and the scope is changed. CISA rates it automatable with total technical impact, meaning attackers can exploit it at scale and take full control of the component. CISA confirms active exploitation; ransomware use is unknown.

Who is affected

For Cisco Identity Services Engine Software, the record lists specific releases in several branches: four 3.1.0 patch releases (p8 to p11 as listed), 3.2.0 p7, three 3.2 patches, 11 listed 3.3 patches, 3.4.0 plus 6 listed 3.4 patches, and 3.5.0 plus three listed 3.5 patches. Cisco ISE Passive Identity Connector 3.4.0 and 3.5.0 are also affected. The CVE record names no fixed version for either product.

Written with AI from the data on this page and checked against it automatically.

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.

CISA required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk guidance and CISA’s “Forensics Triage Requirements”. 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.

CISA notes

Affected and fixed versions

From the CVE record published by the vendor or CVE numbering authority.

  • Cisco Identity Services Engine Software
    Affected
    • 3.1: 3.1.0 p8, 3.1.0 p9, 3.1.0 p10, 3.1.0 p11
    • 3.2: 3.2.0 p7
    • 3.2P: 3.2 Patch 8, 3.2 Patch 9, 3.2 Patch 10
    • 3.3P: 3.3 Patch 1 … 3.3 Patch 11 (11 versions)
    • 3.4: 3.4.0
    • 3.4P: 3.4 Patch 1 … 3.4 Patch 6 (6 versions)
    • 3.5: 3.5.0
    • 3.5P: 3.5 Patch 1, 3.5 Patch 2, 3.5 Patch 3
    Fixed in
    not stated
  • Cisco ISE Passive Identity Connector
    Affected
    • 3.4.0
    • 3.5.0
    Fixed in
    not stated

How to fix it

  • The CVE record names no fixed version – check the vendor advisory and CISA's required action for updates and mitigations.
  • Vendor advisory: sec.cloudapps.cisco.com/security/center/content/CiscoSecu…
  • CISA's deadline for US federal agencies: 2026-09-19 (passed) – a useful benchmark for everyone else, too.

What to do

  1. Check the Cisco advisory for fixed releases or patches and apply them to all ISE and Passive Identity Connector nodes.
  2. Apply mitigations according to Cisco's instructions, as CISA's required action states.
  3. Restrict network access to ISE APIs and management interfaces; keep them off the internet.
  4. Check affected devices for signs of compromise, following CISA's forensics triage requirements.
  5. If mitigations are unavailable, follow BOD 26-04 guidance or discontinue use of the product, as CISA directs.

The CVE record names no fixed version, which does not mean no fix exists. Follow the Cisco advisory for fixed releases and apply its mitigations. Meanwhile, limit network access to ISE APIs and management interfaces, and check for signs of compromise. CISA requires applying vendor mitigations, or discontinuing use of the product if mitigations are unavailable.

Written with AI from the data on this page and checked against it automatically.

CISA's assessment (SSVC)

Exploitation
Exploited in the wild
Automatable
Yes – attackers can automate it at scale
Technical impact
Total – full control of the component or total information disclosure

Weakness: CWE-648 Incorrect Use of Privileged APIs

Questions about CVE-2026-76460

Does an attacker need credentials?
No. The vulnerability lets an unauthenticated, remote attacker bypass authentication by reaching an affected API endpoint, without user interaction.
Is this vulnerability being exploited?
Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2026-09-16 with a US federal due date of 2026-09-19. Whether it is used in ransomware campaigns is unknown.
Which version should I upgrade to?
The CVE record names no fixed version. Consult the Cisco advisory for fixed releases and mitigations for your ISE or Passive Identity Connector branch.

Written with AI from the data on this page and checked against it automatically.

References

Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-21. Always confirm with the vendor's or distribution's advisory before patching.