High [CVE-2026-20352] Cisco Identity Services Engine RADIUS Denial of Service Vulnerability
This high-severity Cisco advisory covers CVE-2026-20352 affecting Identity Services Engine Software.
Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.
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
A vulnerability in the RADIUS feature of Cisco Identity Services Engine (ISE) could allow an unauthenticated, remote attacker to cause a denial of service (DoS) condition on an affected device.
This vulnerability is due to improper handling of certain RADIUS requests. An attacker could exploit this vulnerability by sending a crafted RADIUS request directly to an affected device.
A successful exploit could allow the attacker to cause the ISE node to become unavailable. For single node deployments in that condition, endpoints that have not already authenticated would be unable to access the network until the node comes back up on its own.
Cisco has released software updates that address this vulnerability. There are no workarounds that address this vulnerability.
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 product named by the advisory: Identity Services Engine Software.
- Scope: This vulnerability affects Cisco ISE Policy Service Nodes (PSNs) if they have RADIUS services enabled.
- 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.5 (first fixed: 3.5 Patch 4)
Official advisory · high-confidence parse· fetched 13 days ago·verify at source
- 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.
- 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.5: upgrade to 3.5 Patch 4.
- There are no workarounds that address this vulnerability.
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.