CVE-2026-20029 — Cisco Identity Services Engine XML External Entity Processing Information Disclosure Vulnerability
A vulnerability in the licensing features of Cisco Identity Services Engine (ISE) and Cisco ISE Passive Identity Connector (ISE-PIC) could allow an authenticated, remote attacker with administrative privileges to gain access to sensitive information. This vulnerability is due to improper parsing of XML that is processed by the web-based management interface of Cisco ISE and Cisco ISE-PIC. An attacker could exploit this vulnerability by uploading a malicious file to the application. A successful exploit could allow the attacker to read arbitrary files from the underlying operating system that could include sensitive data that should otherwise be inaccessible even to administrators. To exploit this vulnerability, the attacker must have valid administrative credentials.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 6.2% (30-day exploitation probability)+14
- Technical severity (medium)+3
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Cisco Cisco Identity Services Engine Software).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- EPSS ahead of 93% of scored CVEs: prioritize it in the patch queue.
- Search available logs for exploit probes matching the vulnerability class (injection), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Cisco | Cisco Identity Services Engine Software |
version 3.2.0 p5version 3.4 Patch 3version 3.3 Patch 7version 3.4 Patch 2version 3.3 Patch 6version 3.3 Patch 5version 3.1.0 p10version 3.4 Patch 1 and 23 moreversion 3.3 Patch 4version 3.2.0 p7version 3.4.0version 3.3 Patch 3version 3.3 Patch 1version 3.3 Patch 2version 3.1.0 p9version 3.2.0 p6version 3.1.0version 3.1.0 p8version 3.2.0 p4version 3.2.0 p3version 3.3.0version 3.1.0 p7version 3.2.0 p2version 3.1.0 p6version 3.2.0 p1version 3.1.0 p5version 3.1.0 p4version 3.2.0version 3.1.0 p2version 3.1.0 p3version 3.1.0 p1 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 4.9 | CVSS 3.1 | Medium | 1.2 | 3.6 | psirt@cisco.com via NIST National Vulnerability Database |
| 4.9 | CVSS 3.1 | Medium | — | — | cisco via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N (score shown at the top: psirt@cisco.com) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
EPSS over time FIRST
Oct 13, 2026 → Oct 15, 2026 · 3 reading(s) · max 6.21%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
- Look for parameters with command/query metacharacters and unexpected child processes of the service.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · cisco/cisco identity services engine software
- SSVC assessment updated
- Record published
- CVSS changed · 4.9
- Source status changed · → Deferred
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
1 on the record
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2026-76460 Cisco Identity Services Engine Incorrect Use of Privileged APIs Vulnerability KEV 29d
- Medium CVE-2026-76449 Cisco Identity Services Engine SQL Injection Vulnerability 29d
- Medium CVE-2026-76450 Cisco Identity Services Engine SQL Injection Vulnerability 29d
- Medium CVE-2026-76451 Cisco Identity Services Engine Certificate Management SQL Injection Vulnerability 29d
- Medium CVE-2026-76446 Cisco Identity Services Engine External Entity Injection Vulnerability 29d
- Medium CVE-2026-76447 Cisco Identity Services Engine Certificate Reload Vulnerability 29d
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 fixed version, patch or mitigation documented.
- 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 record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-20029 is "Cisco Identity Services Engine XML External Entity Processing Information Disclosure Vulnerability", rated Medium. It affects Cisco Identity Services Engine Software (Cisco); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 4.9 describes technical severity. EPSS 6.21% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.