Skip to content
VulniPulse
Sign in
Medium4.9Cisco PoC reported

Medium [CVE-2026-20029] Cisco Identity Services Engine XML External Entity Processing Information Disclosure Vulnerability

This medium-severity Cisco advisory covers CVE-2026-20029 affecting Cisco Identity Services Engine Software, ISE.

cisco-sa-ise-xxe-jWSbSDKt Published Jan 7, 2026Updated by vendor Jan 7, 2026
CVE-2026-20029
Affected products & platforms
CiscoISEIdentity Services Engine
Open vendor advisory

Android app · Google Play

Monitor future Cisco CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery
Get CVE alertsSee app features

Summary

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 tha…

Affected products named by the advisory: Cisco Identity Services Engine Software.

Affected versions
  • Scope: At the time of publication, this vulnerability affected Cisco ISE and Cisco ISE-PIC, regardless of device configuration.
  • Earlier than 3.2 — Migrate to a fixed release
  • Release 3.2 (first fixed: 3.2 Patch 8)
  • Release 3.3 (first fixed: 3.3 Patch 8)
  • Release 3.4 (first fixed: 3.4 Patch 4)

Official advisory · high-confidence parse· fetched 2 months ago·verify at source

Fixed versions
  • 3.2 Patch 8
  • 3.3 Patch 8
  • 3.4 Patch 4

Official advisory · high-confidence parse· fetched 2 months ago·verify at source

Mitigation checklist

Recommended fix / mitigation
  • Upgrade to the first fixed release for your train per the Fixed Releases table in this advisory.
  • Earlier than 3.2: migrate to a fixed release.
  • Release 3.2: upgrade to 3.2 Patch 8.
  • Release 3.3: upgrade to 3.3 Patch 8.
  • Release 3.4: upgrade to 3.4 Patch 4.
Workaround status
  • There are no workarounds that address this vulnerability.

Official advisory · high-confidence parse· fetched 2 months ago·verify at source

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.