CVE-2026-76460: Cisco ISE authentication bypass is actively exploited

Quick Answer

Cisco reports active exploitation of CVE-2026-76460, an authentication bypass affecting vulnerable ISE and ISE-PIC releases regardless of configuration. Identify the release and patch level on every node, preserve off-device evidence, and install the matching Cisco fix. Investigate in parallel: an update does not rule out earlier exploitation, and a Known Exploited Vulnerabilities (KEV) catalog entry does not prove that your deployment was compromised.

Verification scope: Vendor evidence and CISA KEV catalog 2026.10.02 checked on 2026-10-02 UTC. Catalog membership establishes reported exploitation, not compromise of this deployment. Recheck the live advisory before production changes.

Status At A Glance

Product scope	Cisco — Identity Services Engine
CVE	CVE-2026-76460
TechGeeks response tier	P0 — confirm an exact match and act now
CISA KEV added	2026-09-16
Vendor severity	Critical
CVSS	CVSS 3.1 base 10.0 — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
Ransomware field	Unknown — this is not the same as No; CISA has not marked the field Known.
Forensic-triage field	Yes — CISA's record calls for forensic triage.
CWE	CWE-648
Federal remediation date	2026-09-19 — applies to covered federal agencies; other organizations should set a risk-based deadline.

What Happened

Cisco Identity Services Engine Incorrect Use of Privileged APIs Vulnerability. Cisco Identity Services Engine (ISE) and Cisco ISE Passive Identity Connector (ISE-PIC) contain an incorrect use of privileged APIs vulnerability that could allow an unauthenticated, remote attacker to gain unauthorized access to the affected device by bypassing the web-based management interface. CISA's KEV listing confirms exploitation evidence, but it does not state how widespread the activity is or prove that any particular installation was compromised.

Affected Scope

Check both ISE and ISE-PIC deployments, including every node in a distributed deployment. The release and patch level determine which Cisco fix applies; the vulnerability does not require a particular device configuration.

Record each node's role and management exposure alongside its installed release. Use that inventory to plan the update and identify the systems and external logs needed for investigation.

What To Do Now

1. Confirm. Inventory every Identity Services Engine asset and record its exact version, patch level, role, relevant configuration, and exposure.
2. Preserve. Save UTC timestamps, off-device authentication, firewall, proxy, DNS, endpoint, application, and SIEM evidence before logs rotate or a disruptive change removes context.
3. Contain. Restrict unnecessary internet and management-plane access using supported controls. Follow the live advisory: Open the live Cisco advisory.
4. Remediate. Install the fixed patch for each node's software train. If malicious activity is suspected, involve Cisco Technical Assistance Center (TAC) and follow the re-imaging guidance below.
5. Validate. Verify the resulting version or patch level, service health, logging, expected access, an expected denial, and representative dependent workflows.
6. Escalate. If exposure overlapped the vulnerable period or evidence is suspicious, treat the system as a potential incident and follow vendor and incident-response recovery guidance.

Fixed Releases And Mitigation

Investigation And Recovery

Review ise-kong/access.log and support-bundle API gateway logs on every node, and cross-check network and firewall logs outside ISE. Cisco warns root access may let an actor remove or hide evidence and strongly recommends re-imaging when malicious activity is suspected. CISA marks forensic triage Yes.

If root or management access may have been obtained, preserve evidence and scope affected accounts and downstream systems. Rotate exposed credentials or certificates when justified, and follow Cisco TAC or incident-response guidance for a trusted rebuild. Patch completion alone does not establish eradication.

Exploitation Evidence

Vendor statement: Cisco PSIRT is aware of active exploitation of this vulnerability.

CISA statement: CVE-2026-76460 was added to KEV on 2026-09-16. The ransomware field is Unknown, and the forensic-triage field is Yes. These are separate signals.

Validation And Boundaries

This notice does not prove that every product carrying the family name is affected, that exploitation is widespread, that a clean indicator search rules out compromise, or that a successful update restored trust. TechGeeks has not reproduced the exploit and does not replace the vendor advisory, asset inventory, vulnerability scanner, or incident-response process.

Related TechGeeks Resources

• TechGeeks Security Notice Center
• All Security Notices
• What to Do When a Device Hits CISA KEV
• Router CVE Exposure, Version, and Mitigation Checklist
• IoT Firmware Update and End-of-Support Checklist
• Live Protect and Runtime Vulnerability Shielding

References

• Cisco advisory or support notice
• CISA guidance
• CISA guidance
• NVD CVE record
• CISA source

Wrap-Up

Record whether CVE-2026-76460 applies to your environment. If it does, assign an owner, preserve the change and investigation evidence, complete the vendor action, and document the validated result.

Correction policy: If a primary source changes affected versions, remediation, exploitation status, or recovery guidance, TechGeeks will update this page and its verification date.