Cisco patches an actively exploited authentication bypass in its ISE network access engine

September 16, 2026. Cisco published a batch of security advisories for Identity Services Engine (ISE), the network access control engine that decides who gets on the network. The same day. The vendor confirmed that at least one of the fixed flaws is already exploited in the wild: CVE-2026-76460, a CVSS 10.0 authentication bypass. September 2026. A hardening release built from an internal audit — conducted with the help of frontier AI models — bundles six further vulnerabilities. Why it matters: bypassing ISE authentication means bypassing the door itself.

ISE is the door to the network

ISE is neither a firewall nor a router. It is the appliance that enforces network access policy: it negotiates 802.1X, answers RADIUS and TACACS+ requests, profiles endpoints, and decides — through VLAN assignment or ACLs — what a machine is allowed to reach once it plugs in. In large organizations, ISE is what turns a wall jack into a controlled connection rather than an open one.

That position makes it a target of unusual value. An attacker who executes code on ISE is not compromising one server among many: they are compromising the machine that grants authorization. From there they can mint accounts, weaken policy, siphon authentication logs, and — most importantly — stay quiet by granting themselves legitimate access to the network. It is the difference between an ordinary pivot point and a crown jewel: you do not reach it for what it contains, but for what it controls.

CVE-2026-76460: an authentication bypass already in use

The most urgent flaw is CVE-2026-76460, rated critical with a CVSS 10.0 score. The vector is unambiguous: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H. A remote, unauthenticated attacker, with no user interaction, achieves high impact on confidentiality, integrity, and availability, with changed scope (S:C) — the compromise crosses a trust boundary.

The root cause is CWE-648, incorrect use of privileged APIs: an API endpoint has insufficient authentication control. A crafted request to that endpoint lets an attacker bypass the web-based management interface and reach the device without credentials. Cisco notes that a successful exploit can lead to command execution with root privileges.

Three details make this worse. First, the flaw affects ISE and ISE-PIC (the Passive Identity Connector) regardless of configuration — no configuration protects you. Second, Cisco confirms active exploitation: the bug was found not by an audit, but while resolving a TAC support case. Third, there is no workaround — the only software fix is the upgrade.

The root reach has a direct consequence for detection. An attacker at that level can erase evidence of their presence, so Cisco advises not to trust the device’s own logs alone: cross-check external network and firewall logs for unexpected uploads or connections to suspicious addresses.

A hardening release built on an AI-assisted audit

Alongside the bypass, Cisco published a hardening release (cisco-sa-hardening-ise-XU5EwX5T) bundling six vulnerabilities found during an internal security review. The telling detail is in the “Source” field: these flaws were found “using existing testing processes as well as frontier AI models.” It is the concrete application of the strategy Cisco described in its post on AI-accelerated vulnerability discovery.

Each CVE here maps to a weakness class (CWE) rather than a single bug — a deliberate choice by Cisco to group issues by nature and keep the disclosure legible.

Two 10.0 scores and two 9.9 in a single hardening release is a rare signal. The headline is not the count but the nature: injection and access control classes on a product whose entire job is access control.

The September 16 batch goes further. Other advisories cover RCE in ISE (CVE-2026-20211, CVE-2026-20176, CVE-2026-20307, at 9.9), authenticated RCE and API flaws (CVE-2026-20282 and related, at 9.1), command injection (CVE-2026-20306, 9.1), and a RADIUS denial of service (CVE-2026-20352, 8.6). RADIUS deserves attention: it is the protocol through which ISE answers authentication requests from network gear, so a denial of service on that flow blocks connections to the network — not just the admin console.

What an attacker gets once root

Let us name the impact precisely. With root on ISE, an attacker does not “read files”: they change network access policy in real time. They can create a phantom local user, disable the posture checking that verifies endpoint compliance, open a sensitive VLAN to a segment they control, or exfiltrate the account and certificate store. All of it looks like legitimate configuration, because the appliance itself produced it.

It is also an ideal persistence machine. Because ISE receives and logs every authentication attempt on the network, an attacker installed there watches credentials pass by and can choose the next targets with a visibility few positions offer. Cisco’s advice to re-image compromised nodes rather than clean them is not excessive caution: with root access, you can no longer trust a machine to attest to its own integrity.

What to do

Five actions, in priority order:

• Patch ISE immediately. The authentication bypass is exploited and has no workaround: the window is not a question of “if,” but of “who is already through.” Fixed releases are 3.1 Patch 12, 3.2 Patch 11, 3.3 Patch 12, 3.4 Patch 7, and 3.5 Patch 4.
• Until then, restrict the management plane. Cisco recommends iACLs (infrastructure access lists) allowing only strictly necessary management and control-plane traffic to the device. It is a bandage, but it shrinks the bypass’s surface.
• Check for past exploitation. On every node, inspect access.log for suspicious usernames — Cisco provides show logging application ise-kong/access.log | include dummyuser — and cross-check external firewall and network logs.
• Re-image any suspect node. If malicious activity is suspected, Cisco recommends re-imaging the node and restoring from a configuration backup, not “cleaning” it.
• Treat ISE-PIC like ISE. The Passive Identity Connector shares the same flaws; ISE 3.0 has reached end of maintenance and must be migrated to a fixed release.

Release 3.4 is the last supported release for ISE-PIC, which has reached end of sale: estates still relying on that appliance should plan migration in the same window as the upgrade.

Verdict

If you run ISE in production, treat CVE-2026-76460 as an incident in progress, not routine patching: it is exploited, has no workaround, and yields root on the appliance that controls network access. Upgrade to the fixed release on your 3.x branch and apply iACLs on the management plane in the same maintenance window. If you cannot patch today, restricting the management plane with ACLs is the only measure that genuinely reduces exposure in the meantime. In every case, re-image any node where any doubt of exploitation remains — root access invalidates trust in the machine’s own logs.

References

• Cisco — Identity Services Engine Authentication Bypass Vulnerability (CVE-2026-76460)
• Cisco — Identity Services Engine Hardening Release: September 2026
• Cisco — Advance Notification for Publication of September 16, 2026, Security Advisories
• Cisco Blog — Strengthening the Foundation: A Predictable, Customer-Focused Response to AI-Accelerated Vulnerability Discovery