Critical [CVE-2026-20305 +1] Cisco Identity Services Engine Command Injection Vulnerabilities
This critical-severity Cisco advisory covers CVE-2026-20305 and CVE-2026-20306 affecting ISE Passive Identity Connector, Identity Services Engine Software.
Aggregated and source-linked by VulniPulse. Data sources, validation and limitations. This bulletin covers 2 CVEs; its score, affected versions and guidance may apply to different issues within that bulletin.
VulniPulse record published Record updated
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.
Summary
Multiple vulnerabilities in Cisco Identity Services Engine (ISE) and Cisco ISE Passive Identity Connector (ISE-PIC) could allow an authenticated, remote attacker to perform command injection attacks on an affected device and execute arbitrary commands as the root user. 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.
This advisory is part of a group of advisories. For a complete list of the advisories and links to them, see Cisco Advance Notification for Publication of September 16, 2026, Security Advisories.
In addition, for further documentation of improvements and fixes in Cisco Identity Services Engine, see Cisco Identity Services Engine Security Hardening Release: September 2026.
Affected products named by the advisory: Identity Services Engine Software.
- 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 12)
- Release 3.2 (first fixed: 3.2 Patch 11)
- Release 3.3 (first fixed: 3.3 Patch 12)
- Release 3.4 (first fixed: 3.4 Patch 7)
- Release 3.51 (first fixed: 3.5 Patch 4)
- Release 3.4 Patch 4 and later (first fixed: 3.4 Patch 7)
- Release 3.51 Patch 3 (first fixed: 3.5 Patch 4)
Official advisory · high-confidence parse· fetched 13 days ago·verify at source
- 3.1 Patch 12
- 3.2 Patch 11
- 3.3 Patch 12
- 3.4 Patch 7
- 3.5 Patch 4
Official advisory · high-confidence parse· fetched 13 days ago·verify at source
Mitigation checklist
- 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 12.
- Release 3.2: upgrade to 3.2 Patch 11.
- Release 3.3: upgrade to 3.3 Patch 12.
- Release 3.4: upgrade to 3.4 Patch 7.
- Release 3.51: upgrade to 3.5 Patch 4.
- Release 3.4 Patch 4 and later: upgrade to 3.4 Patch 7.
- Release 3.51 Patch 3: upgrade to 3.5 Patch 4.
- There are no workarounds that address these vulnerabilities.
Official advisory · high-confidence parse· fetched 13 days 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.