Cisco ISE Auth Bypass Zero-Day CVE-2026-76460 Actively Exploited

Cisco ISE Zero-Day (CVSS 10.0) Under Active Attack, Bypasses Auth

CRITICAL
September 17, 2026
5m read
VulnerabilityPatch ManagementCyberattack

Related Entities

Organizations

Products & Tech

Cisco Identity Services Engine (ISE) Cisco ISE Passive Identity Connector (ISE-PIC)

CVE Identifiers

CVE-2026-76460
CRITICAL
CVSS:10

Full Report

Executive Summary

On September 17, 2026, Cisco disclosed a critical zero-day vulnerability, CVE-2026-76460, in its Identity Services Engine (ISE) and ISE Passive Identity Connector (ISE-PIC) products. The flaw carries the maximum CVSS score of 10.0 and allows for a complete authentication bypass. Cisco's Product Security Incident Response Team (PSIRT) has confirmed active exploitation of this vulnerability in the wild, prompting an emergency patch release. Due to the severity and active exploitation, the U.S. Cybersecurity and Infrastructure Security Agency (CISA) has added it to its Known Exploited Vulnerabilities (KEV) catalog, requiring federal agencies to patch by September 19, 2026. Successful exploitation could grant an attacker root-level command execution, leading to a full system compromise.


Vulnerability Details

The vulnerability, CVE-2026-76460, is an authentication bypass flaw stemming from insufficient authentication controls on a specific API endpoint within the ISE web-based management interface. An unauthenticated, remote attacker can exploit this by sending a specially crafted HTTP request to the vulnerable API. A successful request bypasses all authentication mechanisms, regardless of the device's configuration, granting the attacker unauthorized access. The ease of exploitation—requiring no authentication or user interaction—and the critical nature of ISE as a network access control gatekeeper contribute to its maximum severity rating.

Affected Systems

The vulnerability affects multiple versions of Cisco's network access control solutions. Organizations using the following products should assume they are vulnerable and prioritize remediation:

  • Cisco Identity Services Engine (ISE): Releases 3.1, 3.2, 3.3, 3.4, and 3.5
  • Cisco ISE Passive Identity Connector (ISE-PIC): Releases 3.0 through 3.5

Cisco has released software updates to address this vulnerability and strongly recommends all customers upgrade to a fixed release. There are no workarounds that can fully mitigate the flaw.

Exploitation Status

Cisco has confirmed that its PSIRT is aware of active, in-the-wild exploitation of CVE-2026-76460. The attackers' specific TTPs have not been fully disclosed, but the goal is to gain unauthorized access to the ISE management interface. Following a successful compromise, attackers could potentially achieve root command execution, allowing them to install backdoors, exfiltrate sensitive network information, or pivot to other parts of the network. The active exploitation led CISA to add the vulnerability to its KEV catalog on September 16, 2026, underscoring the immediate and significant risk to organizations.

Impact Assessment

A successful exploit of CVE-2026-76460 presents a catastrophic risk to an organization's security posture. As ISE is a central component for network authentication, authorization, and accounting (AAA), its compromise effectively dismantles network access controls. An attacker could:

  • Gain Full Control: Achieve root-level access to the ISE appliance, allowing them to alter policies, create rogue administrator accounts, or disable security logging.
  • Bypass Network Segmentation: Modify network access policies to gain access to sensitive, segmented parts of the network.
  • Maintain Persistence: Install malware or backdoors on the ISE appliance, which is a trusted, internal system, making detection difficult.
  • Erase Evidence: Delete or modify logs to hide their activities, frustrating incident response efforts.

Given that ISE often holds credentials and configurations for other network devices, its compromise can serve as a powerful launchpad for broader network intrusion.

Cyber Observables — Hunting Hints

Security teams may want to hunt for the following patterns which could indicate related activity:

Type
Log Source
Value
Cisco ISE Management Interface Logs
Description
Monitor for unexpected or anomalous requests to API endpoints, especially from untrusted IP addresses.
Type
Network Traffic
Value
External connections to ISE management ports
Description
Review firewall and network logs for any connections to the ISE management interface from external or unauthorized internal IP ranges.
Type
User Account
Value
Suspicious or new administrative accounts
Description
Audit ISE for any recently created administrator accounts that do not align with change management records.
Type
Log Pattern
Value
Gaps in logging or disabled logging
Description
Unexplained gaps in ISE logs or alerts indicating that logging services have been stopped could be a sign of compromise.

Detection & Response

Defenders should focus on both identifying vulnerable systems and detecting exploitation attempts.

  1. Identify Vulnerable Systems: Use asset management systems to identify all instances of Cisco ISE and ISE-PIC and their running versions. Compare these against the affected versions list provided by Cisco.
  2. Log Analysis: Scrutinize web access logs for the ISE management interface. Look for unusual URI patterns, requests from unexpected IP addresses, or a spike in 401 Unauthorized or 200 OK responses to API endpoints that don't match legitimate administrative activity. This aligns with D3FEND's Network Traffic Analysis (D3-NTA).
  3. User Account Monitoring: Implement continuous monitoring of administrative accounts on ISE. Any new account creation or privilege escalation outside of a standard change window should trigger an immediate alert, as recommended by D3FEND's Domain Account Monitoring (D3-DAM).
  4. Incident Response: If compromise is suspected, Cisco advises re-imaging the affected appliance from a trusted source and restoring its configuration from a known-good backup. Preserve logs and a forensic image of the compromised system for investigation.

Mitigation

Patching is the only effective, long-term solution. However, some compensating controls can reduce risk.

  1. Patch Immediately: The top priority is to apply the security updates provided by Cisco. This is a Software Update (D3-SU) and is the most critical action.
  2. Restrict Access: As a temporary measure, use infrastructure Access Control Lists (iACLs) or firewall rules to strictly limit access to the ISE management interface. Only allow connections from dedicated, secure management workstations or jump hosts. This falls under D3FEND's Inbound Traffic Filtering (D3-ITF).
  3. Network Segmentation: Ensure the ISE management interface is on a separate, isolated management network, not exposed to the internet or general user networks. This is a form of Network Isolation (D3-NI).
  4. Configuration Hardening: Review and harden ISE configurations according to Cisco's best practices to reduce the attack surface. This aligns with Application Configuration Hardening (D3-ACH).

Timeline of Events

1
September 16, 2026
CISA adds CVE-2026-76460 to its Known Exploited Vulnerabilities (KEV) catalog.
2
September 17, 2026
Cisco publicly discloses the vulnerability and releases emergency patches.
3
September 17, 2026
This article was published
4
September 19, 2026
Deadline for U.S. Federal Civilian Executive Branch (FCEB) agencies to apply patches for CVE-2026-76460.

MITRE ATT&CK Mitigations

Applying the patches released by Cisco is the most critical step to remediate the vulnerability.

Mapped D3FEND Techniques:

Restricting network access to the ISE management interface to only authorized personnel and systems.

Mapped D3FEND Techniques:

Using firewalls or access control lists (iACLs) to block all unauthorized traffic to the management plane.

Mapped D3FEND Techniques:

Audit

M1047enterprise

Regularly auditing ISE logs for suspicious activity, such as failed login attempts or access from unusual locations.

Mapped D3FEND Techniques:

D3FEND Defensive Countermeasures

The primary and most effective countermeasure is to immediately apply the patches provided by Cisco. Given the 'critical' severity, active exploitation, and lack of workarounds, patching should be treated as an emergency change. Organizations should use their patch management systems to identify all affected ISE and ISE-PIC instances and deploy the fixed software versions as soon as possible. Prioritize internet-facing or externally accessible ISE nodes first, followed by those managing critical internal network segments. Before deployment, perform regression testing in a non-production environment if possible, but the risk of exploitation likely outweighs the risk of patch-related issues. After patching, verify that the update was successful by checking the system version and running vulnerability scans to confirm CVE-2026-76460 is no longer detected.

As a critical compensating control, especially if patching is delayed, organizations must implement strict inbound traffic filtering for the ISE management interface. This interface should never be exposed to the public internet. Use network firewalls, web application firewalls (WAF), or infrastructure access control lists (iACLs) to create an explicit allow-list of trusted IP addresses or subnets that are permitted to access the management ports (e.g., TCP/443, TCP/8443). All other traffic should be denied by default. This access should be limited to secure management subnets, jump hosts, or specific administrator workstations. This technique directly mitigates the risk from remote, unauthenticated attackers by preventing them from reaching the vulnerable API endpoint in the first place. Regularly audit these rules to ensure they remain effective and have not been inadvertently relaxed.

Deploy network monitoring tools to establish a baseline of normal traffic patterns to and from the Cisco ISE management interface. Use this baseline to detect and alert on anomalies that could indicate scanning or exploitation of CVE-2026-76460. Specifically, monitor for: 1) connections from new or unauthorized source IPs, 2) unusual User-Agent strings in HTTP headers, 3) a high volume of requests to API endpoints, and 4) large or unexpected data transfers from the ISE appliance. Integrating NetFlow, Zeek, or other network telemetry into a SIEM allows for the creation of high-fidelity alerts. For example, an alert could be triggered if an IP address outside the designated management subnet attempts to connect to the ISE's management port. This provides a crucial detection layer for identifying both exploitation attempts and post-compromise activity.

Timeline of Events

1
September 16, 2026

CISA adds CVE-2026-76460 to its Known Exploited Vulnerabilities (KEV) catalog.

2
September 17, 2026

Cisco publicly discloses the vulnerability and releases emergency patches.

3
September 19, 2026

Deadline for U.S. Federal Civilian Executive Branch (FCEB) agencies to apply patches for CVE-2026-76460.

Sources & References

Cisco warns of Identity Service Engine zero-day exploited in attacks
BleepingComputer (bleepingcomputer.com) September 17, 2026
Cisco Warns of New Zero-Day ISE Auth Bypass (CVSS 10.0) Exploited in Active Attacks
The Hacker News (thehackernews.com) September 17, 2026
Active Exploitation Triggers Emergency Patch for Cisco ISE Zero-Day
SecurityWeek (securityweek.com) September 17, 2026

Article Author

Jason Gomes

Jason Gomes

• Cybersecurity Practitioner

Cybersecurity professional with over 10 years of specialized experience in security operations, threat intelligence, incident response, and security automation. Expertise spans SOAR/XSOAR orchestration, threat intelligence platforms, SIEM/UEBA analytics, and building cyber fusion centers. Background includes technical enablement, solution architecture for enterprise and government clients, and implementing security automation workflows across IR, TIP, and SOC use cases.

Threat Intelligence & AnalysisSecurity Orchestration (SOAR/XSOAR)Incident Response & Digital ForensicsSecurity Operations Center (SOC)SIEM & Security AnalyticsCyber Fusion & Threat SharingSecurity Automation & IntegrationManaged Detection & Response (MDR)

Editorial Standards & Analyst Review

CyberNetSec.io uses automation to assist source monitoring, deduplication, observable extraction, and structured intelligence generation. Published analysis follows human-defined editorial standards and adds defensive context including MITRE ATT&CK, D3FEND, STIX, and Sigma where applicable. Read our editorial policy.

Tags

zero-dayauthentication-bypassnetwork-access-controlNACCiscoKEV

📢 Share This Article

Help others stay informed about cybersecurity threats

🎯 MITRE ATT&CK Mapped

Every tactic, technique, and sub-technique used in this threat has been identified and mapped to the MITRE ATT&CK framework for consistent, actionable threat language.

🧠 Enriched & Analyzed

Observables and indicators of compromise (IOCs) have been extracted and cataloged. Risk has been assessed and correlated with known threat actors and historical campaigns.

🛡️ Actionable Guidance

Detection rules, incident response steps, and D3FEND-aligned mitigation strategies are included so your team can act on this intelligence immediately.

🔗 STIX Visualizer

Structured threat data is packaged as a STIX 2.1 bundle and can be visualized as an interactive graph — relationships between actors, malware, techniques, and indicators.

Sigma Generator

Sigma detection rules are derived from the threat techniques in this article and can be converted for deployment across any major SIEM or EDR platform.