Skip to content
VulniPulse
Sign in
Advisory severityHigh7.5Cisco

High [CVE-2026-20247 +1] Cisco Identity Services Engine SQL Injection Vulnerabilities

This high-severity Cisco advisory covers CVE-2026-20247 and CVE-2026-20300 affecting 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.

cisco-sa-ise-sql-inj-3QTKR947 Source published Source updated

VulniPulse record published Record updated

CVE-2026-20247CVE-2026-20300
Affected products & platforms
CiscoISEIdentity Services Engine
Open source 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) could allow a remote attacker to conduct SQL injection attacks on an affected device.

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 product named by the advisory: Identity Services Engine Software.

Affected versions
  • Scope: These vulnerabilities affect Cisco ISE, regardless of device configuration.
  • 3.2 and earlier — Migrate to a fixed release
  • 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

Fixed versions
  • 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

Recommended fix / mitigation
  • Upgrade to the first fixed release for your train per the Fixed Releases table in this advisory.
  • Release 3.2 and earlier: migrate to a fixed release.
  • 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.
Workaround status
  • 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.