NETWORK INCIDENTS

Exploited now

Remediation guide
Cisco · Identity Services Engine

CVE-2026-76460

Cisco Identity Services Engine Authentication Bypass Vulnerability

CISA KEV
Known exploitedadded 16 Sep 2026; US federal deadline 19 Sep 2026
Exploit likelihood
76%100th percentile · FIRST EPSS, 2026-11-15
Severity
10.0 CriticalCVSS 3.1, Cisco
Last verified
30 Oct 2026against the sources below

1In plain language

A flaw in an API of Cisco Identity Services Engine (ISE) could let a remote attacker who hasn't logged in bypass authentication and gain unauthorized access to the device, bypassing the web-based management interface.

Cisco notes that after successful exploitation, attackers may obtain command execution with root privileges.

Cisco is aware of active exploitation, and CISA lists it as known to be exploited.

2Am I affected?

It affects Cisco ISE and Cisco ISE Passive Identity Connector (ISE-PIC), regardless of device configuration.

Cisco's fix tables list release trains with the first release that includes the fix.

Affected releases are summarised by release train in the Fix table.

Check your version

A command to show the running ISE release and patch: Not stated by vendor.

3Fix

Upgrading closes the hole but doesn't remove an attacker who's already in. Because this is being actively exploited, also do the checks under Was I hit?, and if you find anything, follow Cisco's advice to re-image. our analysis

Upgrade to the first fixed patch for your release. Cisco notes that ISE 3.0 has reached End of Software Maintenance and advises migrating to a supported release that includes the fix.

Cisco's upgrade instructions are in the Upgrade Guides on the Cisco Identity Services Engine support page. Source ↗

ProductReleaseFirst fixed release
Cisco ISE or ISE-PIC3.13.1 Patch 12
3.23.2 Patch 11
3.33.3 Patch 12
3.43.4 Patch 7
3.53.5 Patch 4

4Can't patch tonight?

There are no workarounds. There is a mitigation: to prevent remote exploitation, use infrastructure access control lists (iACLs) to allow only required management and control plane traffic to the device.

Cisco considers workarounds and mitigations temporary solutions until an upgrade to a fixed release is available. Cisco has released software updates that address this vulnerability (table above).

5Was I hit?

To check for attempted exploitation, Cisco says to review the access.log for suspicious usernames, on every node of a distributed deployment. Its non-exhaustive example, run at each node's admin CLI (dummyuser is only Cisco's example username):

> show logging application ise-kong/access.log | include dummyuser

Any entry in the output may indicate malicious activity. For more access.log files, collect a support bundle with debug logs included, using shared key encryption, then decrypt it and find the logs at ./ise/logs/apigateway/access.log.<date>.gz.

If you suspect malicious activity, Cisco strongly recommends re-imaging the affected nodes and restoring from configuration backup if needed.

Attackers with root access may remove or hide evidence, so Cisco strongly recommends also checking network and firewall logs outside the device, for example for unexpected uploads from the device to external IP addresses or downloads from malicious IP addresses.

Because of this, an empty result from the log check doesn't prove the device wasn't compromised. our analysis

CISA's catalog flags this CVE for forensic triage, and its required action points to CISA's BOD 26-04 guidance and its Forensics Triage Requirements. Source ↗

6Sources

Summary of public vendor guidance. Verify against the vendor advisory before acting.

See CVE-2026-76460 in the exploited-now list (exploit likelihood, CISA's description, deadline).

More Cisco guides