Answer in brief
CVE-2026-76460 records a High severity vulnerability in Cisco Identity Services Engine Authentication Bypass Vulnerability. The current sources mark it as known exploited. The current feed maps Cisco/Cisco Identity Services Engine Software (generic), Cisco/Cisco ISE Passive Identity Connector (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. Known-exploitation status makes exposure review time-sensitive. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Cisco/Cisco Identity Services Engine Software (generic), Cisco/Cisco ISE Passive Identity Connector (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Cisco/Cisco Identity Services Engine Softwaregeneric | 3.1.0 p8 || 3.1.0 p9 || 3.3 Patch 2 || 3.3 Patch 1 || 3.3 Patch 3 || 3.4.0 || 3.2.0 p7 || 3.3 Patch 4 || 3.4 Patch 1 || 3.1.0 p10 || 3.3 Patch 5 || 3.3 Patch 6 || 3.4 Patch 2 || 3.3 Patch 7 || 3.4 Patch 3 || 3.5.0 || 3.4 Patch 4 || 3.3 Patch 8 || 3.2 Patch 8 || 3.5 Patch 1 || 3.3 Patch 9 || 3.2 Patch 9 || 3.4 Patch 5 || 3.5 Patch 3 || 3.5 Patch 2 || 3.3 Patch 10 || 3.3 Patch 11 || 3.4 Patch 6 || 3.2 Patch 10 || 3.1.0 p11 | Not reported |
| Cisco/Cisco ISE Passive Identity Connectorgeneric | 3.4.0 || 3.5.0 | Not reported |
Published upstream
Sep 16, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 16, 2026
Added to CISA KEV
Sep 16, 2026
Evidence: source:kev:kev:kev:recordA vulnerability in an API of Cisco Identity Services Engine (ISE) could allow an unauthenticated, remote attacker to bypass authentication. This vulnerability is due to insufficient authentication control on an API endpoint. An attacker could exploit this vulnerability by sending a crafted request to an affected API endpoint. A successful exploit could allow the attacker to gain unauthorized access to the affected device by bypassing the web-based management interface.
Quoted source text, attributed separately from HOL analysis.