What is CVE-2026-20192?

CVE-2026-20192 is Cisco Identity Services Engine Hardening Release - Access Control Vulnerabilities. The supplied enrichment data classifies it as Access Control mapped to CWE-284 Improper Access Control.

Which versions are affected?

Affected product and version evidence is listed in the product table above. Current public advisories should be checked for exact version scope before patch targeting is finalized.

Is there active exploitation?

Active exploitation is not confirmed from current sources for CVE-2026-20192. If exploitation is not confirmed from current sources, teams should document that status and continue monitoring KEV, vendor, and telemetry updates.

No. CVE-2026-20192 is not listed in CISA KEV in the supplied enrichment data. KEV status should be monitored because it can change after initial disclosure or after exploitation becomes publicly confirmed.

Is there a public exploit?

6 public PoC repositories reported; 0 marked weaponized in current dataset. Public exploit or PoC availability should raise triage priority, especially for exposed or business-critical systems.

How can defenders detect it?

Start with web/proxy/WAF logs, application logs, network IDS/IPS where available. Look for vulnerability-class behavior, product errors, suspicious authentication events, exploit probes, and abnormal process activity based only on evidence that applies to the affected product.

How should teams prioritize it?

Prioritize CVE-2026-20192 using CVSS 10, EPSS 0%, KEV status, public PoC status, and asset exposure. Internet-facing, privileged, or business-critical deployments should be handled first.

Are workarounds available?

The supplied mitigation guidance says to apply vendor patches and restrict external exposure until fixed. Fixed-version evidence is listed in the mitigation section above.

Which threat actors are linked publicly?

No public threat actor linkage is confirmed from current sources. Do not attribute exploitation to a threat actor unless the source evidence explicitly supports that linkage.

What should be done in the next 24 hours?

Identify exposed assets running affected vendor/product/version combinations. Prioritize based on EPSS, PoC availability, and external exposure. Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class. Open remediation tickets with affected assets, owners, evidence status, and detection coverage so decisions are traceable.

criticalAccess Controlpublic exploit

CVE-2026-20192

CVE-2026-20192 — Cisco Identity Services Engine Hardening Release - Access Control Vulnerabilities

As part of Cisco's ongoing commitment to proactive security and product quality, the Cisco Identity Services Engine (ISE) and Cisco ISE Passive Identity Connector (ISE-PIC) engineering teams have conducted a comprehensive internal security review. This review resulted in a software hardening release that addresses multiple internally discovered vulnerabilities. The vulnerabilities tracked by CVE-2026-20192 are related to improper access control issues that are grouped under the Common Weakness Enumeration (CWE) Pillar CWE-284.

Published Sep 16, 2026Updated Sep 16, 2026Sources: NVD, Cisco (CNA), GitHub, SOCRadar CTI

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Exploit code

public exploit, none observed

EPSS

ahead of 0% of scored CVEs

Affects

Cisco

52 products listed

CVSS base

critical

Remediation

The vendor's own words where we have them.

Upgrade Cisco Identity Services Engine Software to a fixed release. Apply vendor patches per advisory and restrict external exposure of the affected component until patched.

First 24 hours

Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.

Identify exposed assets running affected vendor/product/version combinations.
Prioritize based on EPSS, PoC availability, and external exposure.
Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.

Affected scope

Vendor, product and version as the advisories word them.

Vendor	Product	Versions	Status
Cisco	Cisco Identity Services Engine Software	3.1.0	Vulnerable
Cisco	Cisco Identity Services Engine Software	3.1.0 p1	Vulnerable
Cisco	Cisco Identity Services Engine Software	3.1.0 p3	Vulnerable
Cisco	Cisco Identity Services Engine Software	3.1.0 p2	Vulnerable
Cisco	Cisco Identity Services Engine Software	3.2.0	Vulnerable
Cisco	Cisco Identity Services Engine Software	3.1.0 p4	Vulnerable
Cisco	Cisco Identity Services Engine Software	3.1.0 p5	Vulnerable
Cisco	Cisco Identity Services Engine Software	3.2.0 p1	Vulnerable
Cisco	Cisco Identity Services Engine Software	3.1.0 p6	Vulnerable
Cisco	Cisco Identity Services Engine Software	3.2.0 p2	Vulnerable
Cisco	Cisco Identity Services Engine Software	3.1.0 p7	Vulnerable
Cisco	Cisco Identity Services Engine Software	3.3.0	Vulnerable

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Availability

High

Confidentiality

High

Integrity

High

Scope

Changed

Attack Complexity

Low

Attack Vector

Network

Privileges Req

None

User Interaction

None

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Source
10	CVSS 3.1	critical	3.9	6	NVD, Cisco (CNA)

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

What this weakness leads to

MITRE's own consequences and mitigations for the weakness class — the authority's wording, not guidance derived from the CVSS vector.

MITRE

CWE-284 · Improper Access Control

Varies by Context::

Mitigation: Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.

Weakness & attack patterns

CWE-284Improper Access Control

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

CAPEC-478 · Modification of Windows Service ConfigurationCAPEC-558 · Replace Trusted ExecutableCAPEC-441 · Malicious Logic InsertionCAPEC-546 · Probe Application MemoryCAPEC-502 · Intent SpoofCAPEC-562 · Modify Shared FileCAPEC-551 · Modify Existing ServiceCAPEC-536 · Data Injected During ConfigurationCAPEC-564 · Run Software at LogonCAPEC-550 · Install New ServiceCAPEC-19 · Embedding Scripts within ScriptsCAPEC-503 · WebView Exposure

T1027.009Obfuscated Files or Information: Embedded Payloads
T1546.004Event Triggered Execution: .bash_profile and .bashrc
T1546.016Event Triggered Execution: Installer Packages

Public exploit

Capability, not use: code existing is a different claim from anyone running it.

Repositories

Detection

Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.

Prioritize edge telemetry for network-reachable Cisco Identity Services Engine Software, Cisco ISE Passive Identity Connector.
Monitor for scanner or exploit-pattern traffic after 6 public PoC repositories were reported.

web/proxy/WAF logsapplication logsnetwork IDS/IPS

Timeline

What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.

2026
Added · CVSS 3.1 10.0 (AV:N)
Sep 16, 2026 · NVD
Initial · CVE published
Sep 16, 2026 · NVD
CVE published by MITRE.
Sep 16, 2026 · SOCRadar CTI

References

1 on the record

sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-hardening-ise-XU5EwX5T
Vendor Advisory, Mitre

Elsewhere on this site

Ciscoevery CVE for this vendor
Access Controlsame class
CWE-284other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record1

What should defenders know first?

CVE-2026-20192 is Cisco Identity Services Engine Hardening Release - Access Control Vulnerabilities, a critical vulnerability affecting Cisco Identity Services Engine Software, Cisco ISE Passive Identity Connector from Cisco. The current evidence does not list it in CISA KEV, and the exploit status is: Active exploitation is not confirmed from current sources for CVE-2026-20192. Public exploit evidence is: 6 public PoC repositories reported; 0 marked weaponized in current dataset. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 10 describes technical severity, while EPSS 0% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.