Exploited in the wildCRITICALCISA KEV

Cisco ISE API authentication bypass exploited as a zero-day; Cisco warns of possible root access

A crafted, unauthenticated request to a Cisco ISE or ISE-PIC API endpoint bypasses the management interface, and Cisco confirms in-the-wild exploitation. Patch to the fixed release for your train, then check API gateway logs on every node.

Cisco Identity Services Engine (ISE) and ISE-PICCVE-2026-76460CVSS10.0CWE-648Identity & access
Published Oct 22, 2026

Cisco PSIRT confirmed active exploitation when it disclosed and patched the flaw on 2026-09-16 1, and CISA added it to KEV the same day 2. No actor, start date or victim count has been published 6.

Sep 16, 20263 daysSep 19, 2026

What you need to know

  • Affects Cisco ISE and ISE-PIC 3.1 through 3.5 in any configuration; 3.0 is out of maintenance and has no fix.
  • A remote, unauthenticated attacker can bypass the web management interface, and Cisco warns this may yield root command execution.
  • Exploited as a zero-day per CyberScoop; Cisco confirms active exploitation and CISA KEV set a 2026-09-19 federal deadline.
  • Fixed in 3.1 Patch 12, 3.2 Patch 11, 3.3 Patch 12, 3.4 Patch 7 and 3.5 Patch 4; there is no workaround, only iACLs as a stopgap.
  • Hunt the ISE API gateway access.log on every node for unexpected usernames, and check off-box firewall logs since attackers may wipe evidence.

What's happening

CVE-2026-76460 is an authentication bypass in an API of Cisco Identity Services Engine (ISE) and the ISE Passive Identity Connector (ISE-PIC), rated CVSS 10.0 1. A remote attacker with no credentials can send a crafted request to an affected API endpoint and gain access to the device without passing through the web-based management interface 1. Cisco says every configuration of both products is affected 1.

Cisco states that its PSIRT "is aware of active exploitation of this vulnerability" and published fixes on 2026-09-16 1. CISA added the CVE to its Known Exploited Vulnerabilities catalog the same day, with a federal remediation deadline of 2026-09-19 2,4. The flaw surfaced while Cisco TAC was working a customer support case, 1, and CyberScoop reports it was exploited before Cisco disclosed and patched it 6.

Cisco has not said when exploitation began, who is behind it or how many organizations were compromised, and no threat actor has been named 3,6. Dark Reading reports the scale of the activity remains unclear 7. A VulnCheck researcher quoted by CyberScoop says root on an ISE appliance would let an attacker change access policy, pull stored credentials and move into the network segments ISE controls 6. Researchers quoted by Dark Reading stress that ISE decides which users and devices can connect, so its compromise carries risk across the wider environment 7.

How it works

Cisco attributes the bug to insufficient authentication control on an API endpoint and classifies it as CWE-648, incorrect use of privileged APIs 1,2. The advisory does not name the endpoint 1. Exploitation needs only network reach to the vulnerable API and one crafted request, with no user interaction 1.

The direct result is unauthorized access that sidesteps the management UI 1. Cisco adds that successful exploitation may give threat actors command execution as root, and that at that level they can remove or hide evidence and indicators of compromise 1. Treat a clean on-box log review as inconclusive for that reason.

Cisco's advisory for this flaw lists a single CVE 1. Cisco shipped other critical ISE fixes on 2026-09-16, and its companion hardening advisory says one improper-access-control (CWE-284) flaw in that bundle is known to be actively exploited, pointing readers to this advisory 8. Cisco has not said whether that refers to CVE-2026-20192 or to this bug; the Cyber Centre marks only CVE-2026-76460 as exploited 2. Patch the companion flaws in the same window.

What to do

In order of priority
  1. 1

    Upgrade to 3.1 Patch 12, 3.2 Patch 11, 3.3 Patch 12, 3.4 Patch 7 or 3.5 Patch 4; Cisco states no workaround addresses the flaw 1.

  2. 2

    Move 3.0 deployments, which are past End of Software Maintenance, to a supported release that contains the fix 1.

  3. 3

    Until patched, apply infrastructure ACLs that permit only required management and control-plane traffic to ISE; Cisco calls this a temporary measure that prevents remote exploitation 1.

  4. 4

    Keep ISE management interfaces on trusted administration networks behind segmentation, and monitor firewall, network and authentication logs for anomalies 2.

  5. 5

    If any sign of compromise appears, re-image the affected nodes and restore from a configuration backup if needed, as Cisco recommends 1.

  6. 6

    After any sign of compromise, rotate secrets held by ISE; a researcher quoted by CyberScoop notes root access on the appliance can be used to extract stored credentials 6.

Detection

  • On each node, review the API gateway log with show logging application ise-kong/access.log and look for usernames that do not belong to your administrators or integrations; Cisco says any such entry may indicate malicious activity 1.
  • Cisco's sample filter uses the placeholder username dummyuser and is explicitly non-exhaustive, so do not treat a single string match as the full hunt 1.
  • For rotated logs, collect a support bundle with debug logs included and shared-key encryption, decrypt it, and review the archives under ./ise/logs/apigateway/ 1.
  • Repeat the review on every node of a distributed deployment, not only the primary administration node 1.
  • Correlate with network and firewall logs outside the appliance for unexpected uploads from ISE to external IPs or downloads from known-malicious IPs, since a root-level intruder can scrub on-box logs 1,5.
  • Inventory ISE and ISE-PIC versions and flag any node below the fixed patch for its train, including 3.0 nodes that cannot be fixed 1.

Timeline

  1. Cisco publishes advisory cisco-sa-ISE-ABP-VNSW7Tn5 with fixes and confirms active exploitation 1

  2. CISA adds CVE-2026-76460 to the KEV catalog 2

  3. Canadian Centre for Cyber Security issues alert AL26-021 2

  4. KEV remediation deadline for US federal civilian agencies 4

Sources

Confirmed by vendor and government. Researched and drafted by the VulnDigest briefs agent from 8 sources, then checked against them by a separate review step on Oct 22, 2026.

Fixed releases confirmed against Cisco's advisory and the Canadian Cyber Centre. Cisco's table prints the 3.5 row as '3.51'; both sources give 3.5 Patch 4 as the fix.

Cisco does not state whether release 3.0 is vulnerable; it says 3.0 is past End of Software Maintenance and customers should migrate to a fixed release.

The KEV addition date (2026-09-16) comes from the Canadian Cyber Centre and news reports; the CISA catalog itself could not be loaded.

The zero-day label rests on news reporting (CyberScoop, SecurityWeek) that exploitation preceded the fix; Cisco has not given a start date.

Cisco's companion hardening advisory says one CWE-284 flaw in its bundle is exploited; Cisco has not clarified whether that means CVE-2026-20192.

Spotted an error? Open an issue on sochub.io.