Answer in brief
CVE-2026-20307 records a Unknown severity vulnerability in Cisco Identity Services Engine Remote Code Execution Vulnerability. The current sources do not mark it as known exploited. The current feed maps Cisco/Cisco Identity Services Engine Software (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. The current sources do not mark it as known exploited. 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). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Cisco/Cisco Identity Services Engine Softwaregeneric | 3.1.0 || 3.1.0 p1 || 3.1.0 p3 || 3.1.0 p2 || 3.2.0 || 3.1.0 p4 || 3.1.0 p5 || 3.2.0 p1 || 3.1.0 p6 || 3.2.0 p2 || 3.1.0 p7 || 3.3.0 || 3.2.0 p3 || 3.2.0 p4 || 3.1.0 p8 || 3.2.0 p5 || 3.2.0 p6 || 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 p72 || 3.1.0 p11 | Not reported |
Published upstream
Sep 16, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 16, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 16, 2026
A vulnerability in the web-based management interface of Cisco ISE could allow an authenticated, remote attacker to execute arbitrary commands on the underlying operating system of an affected device. To exploit this vulnerability, the attacker must have at least low-privileged administrative credentials. This vulnerability is due to insecure deserialization of a user-supplied Java byte stream. An attacker could exploit this vulnerability by sending a crafted serialized Java object to the web-based management interface of an affected device. A successful exploit could allow the attacker to execute arbitrary code on the device and elevate privileges to root. In single-node deployments, successful exploitation of this vulnerability could cause the affected ISE node to become unavailable, resulting in a denial of service (DoS) condition. In that condition, endpoints that have not already authenticated would be unable to access the network until the node is restored.
Quoted source text, attributed separately from HOL analysis.