Skip to content
VulniPulse
Sign in
Critical9.9Cisco

Critical [CVE-2026-20147 +1] Cisco Identity Services Engine Remote Code Execution and Path Traversal Vulnerabilities

This critical-severity Cisco advisory covers CVE-2026-20147 and CVE-2026-20148 affecting Identity Services Engine Software, ISE Passive Identity Connector.

cisco-sa-ise-rce-traversal-8bYndVrZ Published Apr 28, 2026Updated by vendor Apr 28, 2026
CVE-2026-20147CVE-2026-20148
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

Multiple vulnerabilities in Cisco Identity Services Engine (ISE) and Cisco ISE Passive Identity Connector (ISE-PIC) could allow an authenticated, remote attacker to achieve remote code execution or conduct path traversal attacks on an affected device. To exploit these vulnerabilities, the attacker must have valid administrative credentials.

For more information about these vulnerabilities, see the Details section of this advisory.

Cisco has released software updates that address these vulnerabilities. There are no workarounds that address these vulnerabilities.

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

Affected versions
  • Scope: These vulnerabilities affect Cisco ISE and Cisco ISE-PIC, regardless of device configuration.
  • Earlier than 3.1 — Migrate to a fixed release
  • Release 3.1 (first fixed: 3.1 Patch 11)
  • Release 3.2 (first fixed: 3.2 Patch 10)
  • Release 3.3 (first fixed: 3.3 Patch 11)
  • Release 3.4 (first fixed: 3.4 Patch 6)
  • Release 3.51 (first fixed: 3.5 Patch 3)

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

Fixed versions
  • 3.1 Patch 11
  • 3.2 Patch 10
  • 3.3 Patch 11
  • 3.4 Patch 6
  • 3.5 Patch 3

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.1: migrate to a fixed release.
  • Release 3.1: upgrade to 3.1 Patch 11.
  • Release 3.2: upgrade to 3.2 Patch 10.
  • Release 3.3: upgrade to 3.3 Patch 11.
  • Release 3.4: upgrade to 3.4 Patch 6.
  • Release 3.51: upgrade to 3.5 Patch 3.
Workaround status
  • There are no workarounds that address these vulnerabilities.

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.